Previous Posts


Block XP SP3 - Stop the madness

Find out where a DLL, EXE, or SYS file came from

VMWare 2.0 Beta 2 Release

Restrict User Logon Hours

Vista Service Pack 1 is coming your way

Use auditing to track who deleted your files

IntelliAdmin Remote Control - Status Update

Try out the IE 8 Beta

Forward email in Exchange

Keep track of your email in Exchange



Archives

May 2005

January 2006

April 2006

May 2006

June 2006

July 2006

September 2006

October 2006

November 2006

December 2006

January 2007

February 2007

March 2007

April 2007

May 2007

June 2007

July 2007

August 2007

September 2007

October 2007

November 2007

December 2007

January 2008

February 2008

March 2008

April 2008

May 2008



Subscribe to our Feed:






Update your DNS Server - NOW!

I have been struggling with a strange DNS issue on my network for the last month. I have tried everything under the sun, and nothing has worked. The problem was that many times you would need to go to a site twice before it would resolve properly.

Then I heard yesterday that ICANN (The organization that handles the core DNS system for the internet) released a statement back in 2007. The short of what they are saying is that one of the 12 root servers is going to have a different IP address.

This didn't make it to the major news outlets as breaking news (surprise surprise) because something like this is as interesting as watching paint dry.

This means that most administrators had no idea that the IP address had changed (Including me)

I started thinking that this could be the actual cause of my strange DNS issue. I decided to check my DNS server and see if it automatically updated - and of course it did not.

It would seem like a simple change, but this has never happened before. Those 12 servers have had the same IP addresses forever (Well not forever, but for 99% of the internet it has been forever). If there were bugs in the MS DNS server it would be hard to notice if these had not changed before.

To make things worse, according to this blog article ICANN let the IP address go, and some rouge server was put in its place. This means that they had 1/12th of the internet in their hands. Who knows what they did with it. It could have been a good Samaritan move - or it could have been something nefarious. We will probably never know.

After I updated the root hint for l.root-servers.net my DNS resolving started working perfectly again. I find it hard to believe that this was a coincidence (Needed a full reboot for it to take effect).

So the question is, what do you need to do? If you run a Windows DNS server you need to update this root hint manually.

Here is how you do it. Open your the DNS server manager, and right click on the DNS server you want to update

Windows 2003 DNS Properties

Then click on the "Root Hints" tab. See the "L" server entry I have selected below:

Windows 2003 Root Hint Change

Click edit after selecting it, and remove the old IP address of 198.32.64.12 and change it to 199.7.83.42.

After clicking OK you will need to reboot your server. It seems that even restarting the DNS server service will not force it to reload these settings.


Posted By: Steve Wiseman on Tuesday, May 20, 2008

Check out our utilities for windows

 



Copyright © IntelliAdmin, LLC, 2008. All Rights Reserved