From: Jonathan de Boyne Pollard on
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<blockquote cite="mid:hed34q$71a$2(a)tncsrv01.tnetconsulting.net"
type="cite">
<blockquote type="cite">
<p>Wouldn't that effectively multihome the machine, and bring with
it all those related hassles?
</p>
</blockquote>
<p>Yes, as I (mis)understand it, it does.
</p>
<p>However I have never experienced any of the problems that others
say exist with multihomed DCs or boxen.&nbsp; (I'm not saying that they
don't exist, just that I've not run in to them.)
</p>
</blockquote>
<p>The algorithm for the NetLogon service (in very broad view) would be
a simple three-stage affair:&nbsp; Find all of the network interfaces on the
machine; find all of the IP addresses bound to each interface; send the
DDNS Update requests to register them.&nbsp; </p>
<p>I would be quite surprised if there wasn't an exclusion, either of
network interfaces that are marked as loopback interfaces (in the first
stage) or of IP addresses in 127.0.0.0/8 (in the second stage),
preventing the registration of IP addresses and network interfaces that
are not routable outside of the machine itself.&nbsp; This is the sensible
thing to do, and it would be surprising to learn that it wasn't being
done.&nbsp; There's a relatively easy way and documented way to do perform
this sort of exclusion using <a
href="http://msdn.microsoft.com/en-us/library/dd877219%28VS.85%29.aspx">the
<code>SIO_ADDRESS_LIST_QUERY </code>WinSock ioctl</a>, which filters
out machine-local and link-local IP addresses that are bound to
software loopback network interfaces.<br>
</p>
<p>The existence of such a filter would explain why you've never had a
problem, here.</p>
</body>
</html>