We are experiencing a problem since we put in a new domain at a client site. There are two DC's that are configured as DNS servers in the new domain (.160 and .162) and the new domain has a two way trust to the old (2003) domain. We recently discovered that PC's are getting the wrong DNS server info on reboot. They are getting the OLD DNS servers (.10 and .11). If you force them to do an actual DHCP broadcast via ipconfig /renew - they get the right DNS information and show the DHCP server as being the correct, new domain controller (.160).
We are not sure where the old DNS server information is coming from as the old scopes are disabled. We have even spun up a new OS, set the IP configuration to "obtain automatically", joined it to the new domain and on boot, it also gets the "old" DNS server info. Interestingly, we have shut down the DHCP service, rebooted the machine so that it has no IP addressing at all then turned the DHCP service back on and it gets the "old" info (.10 and .11). The only way to get machines to do an actual DHCP broadcast and get the new DNS server info is to perform an "ipconfig /renew".
I have turned on switchport monitoring and performed a packet capture. It would appear that the machines do not perform an actual DHCP broadcast on boot. Is it possible that the lease was set to an extreme amount of time and until that original"old" lease expires the machine will automatically use a "cached" DNS server entry?
We have run a piece of software that looks for rogue DHCP scopes and it has found nothing. I have checked every switch, router and firewall in the network as well. Any insight or help you may have would be much appreciated!
Thank you,
Curtis