We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

sbs 2003 DNS settings reverting to external ISP settings

PaulJohannesMarais
on
Medium Priority
404 Views
Last Modified: 2012-05-11
I notived that our SBS 2003 server was acting strangely.  After further investigation I notived that the DNS settings on the local NIC were pointing to the external ISP DNS servers.  I changed this to point to itself but after a few minutes it reverts back to the enternal IP address.  I have run a search on the entire registry and find that it is only listed on this one interface.  I have tried to change them in the registry but it reverts back to the external addresses after a few minutes.  The single router is not running dhcp, the forwarders on DNS server settings is correct.  Not sure where else to look.
Comment
Watch Question

Commented:
Is the server getting it's address from a DHCP reservation?  If it is, just set it to a static address.  Check that you DHCP server has the SBS server as the primary DNS.

Author

Commented:
no the servers ip address is fixed, and the DHCP settings are configured to point to the fixed ip of the server

Author

Commented:
in the registry, the server interface has a registry setting "Nameserver" which keeps verting back to the external dns settings.  in the same registry key enableDHCP is 0.  

Author

Commented:
Also , originaly there was a problem when you tried to change the DNS settingson the server NIc stating that another network adapter had the same ip address although it wasn't physically connected to the server.  According to a microsoft KB article this can happen when the NIC card is moved to another slot.  I opened the management console showing hidden devices and removed the orphan nic.  It was suffereing the problem of reverting to the external IP addresses before I made this change.

Commented:
Try reseting the internet protocol on the server (http://support.microsoft.com/kb/317518).  This has the effect of removing the stack and reintalling it, and should get rid of any ghosts from the orphan card, which is what is probably causing the problem

Author

Commented:
Waiting for the client to give the go ahead to reboot the server.

Author

Commented:
I have run the netsh reset command and can reboot the server in 1hr 30 minutes.  Will inform you of the result.  FYI, the ip settings were reset to auto assigned (as was mentioned in the KB article).  I set the NIC to the correct setttigns but problem still persists.  I am assuming this is because the server has not been rebooted yet.

Author

Commented:
No joy, DNs settings still reverting back to external IP after 5 minutes or so.  Pulling my hear out on this one

Commented:
Couple more drastic things you could try.  Remove the device driver for the all the NIC and then have the system re-discover them.  Or you could add a new NIC card and move over to it, hoping that the problem doesn't follow.  
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Author

Commented:
Solved problem myself

Author

Commented:
Solved the problem myself
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.