Hello,

I am a bit confused about the nameserver change process.

I am transferring my sites to a new web host. Since I am using the original host's namerservers, I will have to change them for each domain to point to the new server. After I have mirrored all the files and accounts at the new server and if the old server is active while I change the nameservers, will it result in any downtime for www/POP3 services? Note: if the downtime is due to propogation, that is different. My question is regarding the process at the registrar's end.

Some of the domains are at Stargate Inc and others are at Network Solutions Inc. The live support guy at Stargate told me that the nameserver change is instantaneous. Is this true?

Anyone who has experienced this first hand, please respond.

The last time I transferred servers was in 1997 and I do recall some downtime then, but not sure. But that was then...

-Ani

Hi,

There are only 3 Domain Registrars.

1) NSI - they don't appoint dealers/partners but sell on their own or recruit affiliates. When you update/modify any changes to your records.... they will email the adminstrative contact to confirm any changes.

2) ICANN - they appoint partners as they call them to sell domains. To update/modify the records, you need a username and password to go into control panel to make the changes.

3) OPENSRS - they appoint dealers to sell domains for them and to update/modify records, you also need a username and password to go into control panel to make the changes.


In answer to your question when DNS(nameservers-primary & secondary) are modified to point to a new server, it normally takes 24 to 72 hours for the new DNS to propogate before your site on the new server is detected when someone types the url in their browser.

In normal case there should not be any downtime or lose of email if you have mirrored your files/data on new server and your old server is kept alive. But exceptions are always there.

There are only 3 Domain Registrars
=========================

Not true. ICANN is not a regisrar. They are the non-profit governing body of all the registrars for .com, .net and org, as well as the new TLD's.

A list of all registrars that ICANN, Verisign and the DOC accredit can be found at www.icann.org.

Hi Ani,

The changes of your WHOIS record may take up to 24 hours to reflect in the master WHOIS database. Namely, we have seen in several cases, that while the changes in your Registrar's WHOIS database are completed, the default WHOIS database may still show your old nameservers for another 24 hours.

As long as you have a new account with a mirror of all of your old data, and the old account active at the same time, you do not have to worry about downtime. What you have to worry about, though, is the incoming data to the old account due to the propagation step.

Namely, if you have the new account active with the new mailboxes, some mail may still be routed to your old webhost. If you have CGI scripts that dynamically create data in your website, such as a messageboard, then some of the newly created data may be created on the old server, some on the new. Thus, you would be better off, closing all CGI scripts on the old server and display a message that it is temporarily down, or redirect the scripts to your new IP address (which may not be worth all the work, considering propagation only takes from immediate to a maximum of 72 hours).

I confirmed a change for my domain to move to a new host (hosting4less.com) Sunday and although the whois info shows that the dns servers point to them, my site is not going to it


Address of site currently http://www.freakscene.net (@ primemaster.com)

IP of new site @ hosting4less - http://208.50.7.97


Is this normal?

Jeremiah,

I did a traceroute to your site and got the new IP address. I am in India and it seems that the nameserver change has propgated here. It must be your local DNS that is not updated yet. You should check with your ISP.

Hi jeremiah,

It may simply be that it takes a little bit longer for your ISP to get the changes propagated to its network.

Please, wait for a maximum of 72 hours, then if it still doesn't work, contact your ISP and they should walk you step-by-step of the possible causes for your inability to access your website.

thanks guys. I am getting the same thing @ work too.

Hopefully it will rollout by tomorrow.

I appreciate you guys checking it out!!!!

Sometime the records are locked in locan dns cage. You need to refresh the local dns cage memory to make sure if the changes have taken place. It worked fine from here in Australia too.

Hey Sanjay,

I think you meant local DNS cache. Right?