Incorrect IP address returned from DNS

[Rob Nicholson]

I've got a home development network at home that consists of:

o Gandalf: Windows 2003 server acting as domain controller and DNS server
with static IP address of 192.168.0.2
o Frodo: Development PC running Windows XP with static IP address of
192.168.0.4
o Merry: Windows 2003 server running under VMware workstation with DHCP
address currently of 192.168.0.105
o Mordor: Windows XP PC running under VMware workstation with DHCP address
currently of 192.168.0.101
o Wireless router acting as DHCP server with IP address 192.168.0.1

However, when I ping merry from (say) Frodo, it returns the IP address of
192.168.0.101 which is actually the IP address of Mordor. Conversely, ping
mordor from Frodo and it returns the IP address of 192.168.0.105 which is
the IP address of Merry.

It's basically got very confused :-)

All the non-DNS systems have their DNS set to 192.168.0.2, 192.168.0.1, i.e.
use Gandalf the AD DNS server first and if it's offline, use the router
(which resolves to the internet).

I must admit I don't know much about how a Windows network sorts out it's
internal names in DNS when running AD. Does a Windows XP PC say to the DNS
Server "Hey, here I am and my IP address is XYZ?"

Is there a way to have a look in the DNS database on the AD server, e.g.
find what information it's holding for a PC?

And I guess finally, is there a way to refresh the whole darn lot. I'm going
to reboot Gandalf (AD server) to see if that helps.

Thanks, Rob.

[Meinolf Weber]

Hello Rob,

In a domain ALL machines has to use the Domain DNS server (and if you run
DHCP also better use the 2003 DHCP server not the router). Use the router
only for that what it is made for, routing. If you configure the routers
ip as DNS on domain members, login to domain, group policy processing, etc.
will not run correctly. For internet access in the domain configure the FORWARDERS
tab in the DNS server properties under the DNS management console, add here
the ip address from your ISP's DNS servers.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I've got a home development network at home that consists of:
>
> o Gandalf: Windows 2003 server acting as domain controller and DNS
> server
> with static IP address of 192.168.0.2
> o Frodo: Development PC running Windows XP with static IP address of
> 192.168.0.4
> o Merry: Windows 2003 server running under VMware workstation with
> DHCP
> address currently of 192.168.0.105
> o Mordor: Windows XP PC running under VMware workstation with DHCP
> address
> currently of 192.168.0.101
> o Wireless router acting as DHCP server with IP address 192.168.0.1
> However, when I ping merry from (say) Frodo, it returns the IP address
> of 192.168.0.101 which is actually the IP address of Mordor.
> Conversely, ping mordor from Frodo and it returns the IP address of
> 192.168.0.105 which is the IP address of Merry.
>
> It's basically got very confused :-)
>
> All the non-DNS systems have their DNS set to 192.168.0.2,
> 192.168.0.1, i.e. use Gandalf the AD DNS server first and if it's
> offline, use the router (which resolves to the internet).
>
> I must admit I don't know much about how a Windows network sorts out
> it's internal names in DNS when running AD. Does a Windows XP PC say
> to the DNS Server "Hey, here I am and my IP address is XYZ?"
>
> Is there a way to have a look in the DNS database on the AD server,
> e.g. find what information it's holding for a PC?
>
> And I guess finally, is there a way to refresh the whole darn lot. I'm
> going to reboot Gandalf (AD server) to see if that helps.
>
> Thanks, Rob.
>