0

I have a Windows Server 2003. It is connected to a number of networked databases but stopped working this morning. It was receiving DNS from an old DC which we have just retired. I tried to change the settings manually. Afterwards it asked to be restarted. After I restarted it booted back up with the old DNS settings again. Nightmare. I have also discovered an old XP box with the same issue. I am not sure what is doing this. It is picking up DHCP from the correct server which is also one of 2 DNS servers. The DHCP server is set with the right DNS server addresses. However I cant point this one server at it or leave it blank as it changes the DNS back. Please help.

Ciarron
  • 1
  • 1
    Why would it ask to restart on a dns update? set it again it should not ask to be rebooted. – tony roth Jul 11 '13 at 15:12
  • do you get a clean reboot, if the reboot crashes as in you get the message that "the previous reboot was unexpected" then any settings you've made won't stick. – tony roth Jul 11 '13 at 15:18

2 Answers2

1

Check Resultant Set of Policy. Somebody may have used the evil, nasty mechanism in Group Policy that can be used to specify DNS server addresses.

Evan Anderson
  • 141,071
  • 19
  • 191
  • 328
0

Manually set the IP and DNS settings for it. Don't allow an auto assigned DHCP address but use an address from the DHCP pool.

  • i think he said he tried that "I tried to change the settings manually" – tony roth Jul 11 '13 at 15:17
  • I thought he meant only for the DNS settings. I was recommending he manually set the IP address as well. –  Jul 11 '13 at 15:29