"Ace Fekay [MVP]" <PleaseAskMe@SomeDomain.com> wrote in message
news:eIPP$7C$GHA.1200@TK2MSFTNGP02.phx.gbl...
> In news:ic-dnRdXaYTfwt3YnZ2dnUVZ_q2dnZ2d@giganews.com,
> Will <westes-usc@noemail.nospam> stated, which I commented on below:
> > All of our Windows 2003 computers that are doing dynamic updates of
> > DNS to the domain controller's DNS server are updating their domain
> > name to resolve to TWO different IPs. One of these is the IP that
> > is configured for the host by DHCP. But the second IP is one that
> > is always the same across all hosts. It is the address 192.38.0.1.
> > Aside from the strangeness of this being the same address for
> > different computers, what is really strange is that this IP has no
> > bearing whatsoever to the configuration of our network. I do not find
> > this IP in the registry of the affected machines, and I do not find
> > this IP on the file system. Can someone explain to me what might
> > be causing this? It appears to affect only Windows 2003.
> >
> > The dynamic updates to our domain controller's DNS server appear to be
> > accepted with both IPs, but only the correct IP ever gets registered
> > to our DNS. The 192.38.0.1 address mysteriously vanishes and is
> > never stored by DNS server, even if I create an Active Directory
> > integrated reverse zone to hold it (i.e., 192.38.0.x). It seems
> > that this IP 192.38.0.1 is reserved by Microsoft for some special
> > use, but I'm baffled so far, and I find no references to it online.
>
> I'm assuming that the domain controllers are single homed (one NIC in use
on
> one subnet)? But I can't understand why you would have a domain controller
> configured for DHCP, unless I mis-read your post and don't know what you
> mean by "it is configured for the host by DHCP"?

The domain controller is single homed and has a static IP. The DHCP hosts
are the Windows 2003 server member servers.

It is the Windows 2003 member servers that are exhibiting this weird
behavior of trying to register 192.38.0.1.


> I looked up 192.38.0.1 using nslookup, however it returns nothing.
Arin.net
> says it belongs to RIPE, which is based in Amsterdam. So this does not
make
> sense as to why the DCs are registering this IP. Normally the interface's
IP
> will get registered into the DNS server that is configured in IP
property's
> zone, unless there's a mixture with ISP and local DNS servers.

Again, it's not the domain controllers that are registering this IP. It is
all of our Windows 2003 member servers.


> ANy errors in the Event logs?

None that I can find anyway.

--
Will