So I have a Server 2008 machine which also acts as a PDC, and provides DNS to all other machines. Now, the server has 2 NICs, one on a 172.16.0.0/24 LAN, and one on a 192.168.47.0/24 LAN. Every other machine on the network has one NIC, and belongs to one network or the other.
DHCP is working fine, but hostname/DNS lookups using the server name of the PDC sometimes resolves to the wrong NIC.
Now, DNS does have hostname entries for the pdc for both addresses, but I can’t have a computer not on that network getting a resolved address it can’t reach.
Ex: Computer pdc1 has addresses 192.168.47.1 and 172.16.0.1. Client client1 has a NIC physically on the 192.168.47 network. For that reason, DHCP works fine, it gets an address. However, when it looks up the address for pdc1, it gets 172.16.0.1, which isnt reachable and causes lots of problems.
My question is, what is the standard way to prevent this situation? I know I’m not the only one with a PDC on separate NICs, where the client computers need to look up the server name and get the address on the network it’s actually on.
I know a cheap solution is to add the correct address to each clients host file, but this is a workaround since the relationship is now managed on each client pc and not the domain controller.
Any tips are appreciated!
Answer
By default Microsoft DNS server use round robin when serving DNS queries. It means it returns one or another address in circural fashion.
In your case, you should reconfigure it to use network prioritization, according to this document:
Comments
Post a Comment