Click to See Complete Forum and Search --> : Site Accessibility after Nameserver and A-Record Changes


Thomas2
10-07-2006, 08:08 AM
Hi,

Could somebody please explain to me why, when I change webhosts, my website can not be reached at all (neither under the new location nor the old one) for about 5-6 hours (for a .uk domain) after I changed the name servers (not only over my own ISP, but also from elsewhere (as an external monitoring service as well as my access logs confirmed)).
On the other hand, as I tested out now with an unused domain, when I merely change the A-record (leaving the name server unchanged), my website is not offline at all (with some ISPs being served from the new webhost and some from the old (before the new A-Record has fully propagated)).

In this respect, I wonder whether a seamless transition in case of a webhost change is possible by first changing the A-record (and MX record) and after this has fully propagated, changing the name servers. Or if not, what would be the best way to avoid any downtime when changing webhosts? (some sources claim that there should not be any downtime after changing name servers if both the old and new webhost can in principle still be reached, but this is not my experience as mentioned above).

Thomas

dotancohen
10-12-2006, 09:26 PM
You need to FTP the files of your website to the new host.

Thomas2
10-15-2006, 04:56 AM
You need to FTP the files of your website to the new host.

This is not the problem. Assume that everything is in place both at the old and new host.

Thomas

bathurst_guy
10-15-2006, 06:44 AM
I wonder whether a seamless transition in case of a webhost change is possible by first changing the A-record (and MX record) and after this has fully propagated, changing the name servers.
That sounds like a good way to do it then.

hitchhiker
10-15-2006, 01:33 PM
sounds brilliant . . . anyone done the same and it worked for them?