
April 23rd, 2008, 02:35 PM
|
|
Registered User
|
|
Join Date: Apr 2008
Posts: 1
Time spent in forums: 24 m 14 sec
Reputation Power: 0
|
|
|
Second name servers gets cached in DNS
I have 2 Windows 2003 webservers. One is NS1 which has a unique set of IPs and firewall, and the second one is my NS2 server which sits on a totally separate network with its own bank of public IPs and firewall.
Here is what is happening: All of my domains have NS1 and NS2 with different IPs. I was trying to do a test to see if the website would go to NS2 if NS1 was not available. I went to my NS1 server and disabled one of my websites under IIS. After 2 or 3 minutes the website query went straight to NS2. Everything seemed to work fine. The problem was that it stays on NS2 even after a re-enable the NS1 server. I have waited 2 days and my servers DNS appears to be ached and still shows NS2. We tried everything from clearing the DNS, rebooting the servers and the routers and nothing. The problem is not locally only. My customers also see the problem on their end. If I have them ping the website after NS1 is re-nabled, their ping still points to the NS2 even after a couple of days.
Any ideas? I can't figure this one out or how to setup an NS2 server for backup.
Any help will be greatly appreciated.
Thank you.
Alex Carvajal
|