ZeroHour Posted January 27, 2009 Posted January 27, 2009 Hi We have a migrated DHCP from Windows 2000 to Windows Server 2008 and I went to change our DNS server entries (change the second DNS to a new DC ip) but after making the change XP clients are only getting the FSMO DNS (which should be DNS 1) and not the changed second DNS entry. I tried reordering the list so the new DNS ip was first but clients still receive only the FSMO ip as a DNS server. The strange thing is a standalone vista client gets both IP's and seems to work correctly. I added a gateway ip to the DHCP and XP clients got that change but they just wont update DNS ip's Am I doing something silly or should this not just work? Any ideas? Cheers
Jay Posted January 27, 2009 Posted January 27, 2009 at the risk of sounding daft, have you cleared the XP machines DNS cache?
ZeroHour Posted January 27, 2009 Author Posted January 27, 2009 at the risk of sounding daft, have you cleared the XP machines DNS cache? Yeh I did all the ipconfig switches and cleared DNS/DHCP entries from the server before /renew'ing DNS hasn't been set in a GPO has it? It can be set in GPO?!?!
SYNACK Posted January 27, 2009 Posted January 27, 2009 It can be set in GPO?!?! Computer Configuration -> Administrative Templates -> Network -> DNS Client : DNS Servers 1
ZeroHour Posted January 27, 2009 Author Posted January 27, 2009 Does not appear to be set there. I did a wireshark sniff and dhcp is sending 2 dns servers back in the packet.
SYNACK Posted January 27, 2009 Posted January 27, 2009 You could try reseting the ip stack on one of the stations to see if this gets rid of the old settings, if so you know it is probably another bug: How to reset Internet Protocol (TCP/IP) in Windows XP You could also try reseting the DNS with a VBS script to see if that sticks any better than the DHCP settings change: Modify the DNS Server Search Order for a Network Adapter 1
ZeroHour Posted January 28, 2009 Author Posted January 28, 2009 You could try reseting the ip stack on one of the stations to see if this gets rid of the old settings, if so you know it is probably another bug: How to reset Internet Protocol (TCP/IP) in Windows XP That seems to have worked. Thanks so much Now to figure out a way to deploy it.... or the cause...
SYNACK Posted January 28, 2009 Posted January 28, 2009 (edited) That seems to have worked. Thanks so much Now to figure out a way to deploy it.... or the cause... Your welcome, I'd just chuck it in a batch file as the last shutdown script in the machines GPO, its just the one command so you may not even have to copy the TCPreset batch file to the local drive before executing it. Edited January 28, 2009 by SYNACK
ZeroHour Posted January 28, 2009 Author Posted January 28, 2009 Found the cause. The unattended file had a dns search order set in it with the one server listed. Cant believe dhcp did not override it.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now