Hi,
We're transferring a lot of accounts to a new server. We use the 'Express Method' and when the DNS records exist on the old server and we set the TTLs real low ahead of time the transfer is nearly instantaneous.
HOWEVER, a couple sites have DNS that is managed elsewhere with only an A record pointer. The problem is that we've experienced some pretty large delays in everything propagating to the new server on different connections. The site we're dealing with currently has DNS hosted by Yahoo Business. We edited the A record there shortly after the transfer, but it's been 2 days and the client called to complain that a customer was still seeing the 'Site moved' page that is linked in the .htaccess file. When we test the domain at DNSTools, the new IP shows.
We know that DNS can take a while to propagate, caches may need to be cleared, etc. But no average customer is going to know that and our client may be losing business in this 'downtime'.
- Is there a way to set a redirect in the OLD SERVER'S .htaccess file that would send the user to the new server (instead of the 'Site moved' page)? If so, let me know the syntax, I'm not great with .htaccess commands.
I know I can get to the new site by going to: 'http://ip.ad.dre.ss/~accountname. This takes me to a 404 page on the new site, but it's easy to get around from there. Or I wonder if a redirect could be set on the new site for that issue?
- Any way to implement this in .htaccess or otherwise so there will be NO chance of anyone hitting the old server while we wait for things to propagate?
- How long has anyone seen an A record change take to redirect in a 'worst-case' scenario? The client wants to know when this will clear up.
THANKS!
Kenny
We're transferring a lot of accounts to a new server. We use the 'Express Method' and when the DNS records exist on the old server and we set the TTLs real low ahead of time the transfer is nearly instantaneous.
HOWEVER, a couple sites have DNS that is managed elsewhere with only an A record pointer. The problem is that we've experienced some pretty large delays in everything propagating to the new server on different connections. The site we're dealing with currently has DNS hosted by Yahoo Business. We edited the A record there shortly after the transfer, but it's been 2 days and the client called to complain that a customer was still seeing the 'Site moved' page that is linked in the .htaccess file. When we test the domain at DNSTools, the new IP shows.
We know that DNS can take a while to propagate, caches may need to be cleared, etc. But no average customer is going to know that and our client may be losing business in this 'downtime'.
- Is there a way to set a redirect in the OLD SERVER'S .htaccess file that would send the user to the new server (instead of the 'Site moved' page)? If so, let me know the syntax, I'm not great with .htaccess commands.
I know I can get to the new site by going to: 'http://ip.ad.dre.ss/~accountname. This takes me to a 404 page on the new site, but it's easy to get around from there. Or I wonder if a redirect could be set on the new site for that issue?
- Any way to implement this in .htaccess or otherwise so there will be NO chance of anyone hitting the old server while we wait for things to propagate?
- How long has anyone seen an A record change take to redirect in a 'worst-case' scenario? The client wants to know when this will clear up.
THANKS!
Kenny