Changing Nameservers

[mads]

I just migrated my site from shared hosting to a vps. I had to change the child names for the nameserver.

My site when accessed through true internet is still pulling the data from my old host but if i access the site

through an online proxy browser the site is showing up from new server.

I did ipconfig /flushdns and I deleted my cache...............still the same result.

If i go to just-ping.com I can see the nameservers are pointing to the right ip but not with true internet, this is a joke. Been more than 24 hours now.

[richardt1808]

Hi,

It can take up to 48 hours or more for new name servers to propagate across the globe. There is no pattern as to when each ISP will pick the new ones up, so just be patient as it will resolve itself eventually.

Cheers

[jambla]

Hi,

It can take up to 48 hours or more for new name servers to propagate across the globe. There is no pattern as to when each ISP will pick the new ones up, so just be patient as it will resolve itself eventually.

Cheers

Yup, What richardt1808 said. Be Patient.

[mads]

just frustrating when you can see its already changed everywhere else

[Prasert]

If you have a migration like this coming up again, lower the TTL values of the zone file a few days before the migration. This will decrease the caching time on other nameservers.

After the migration, increase the TTL values again to the old values.

[welo]

If you have a migration like this coming up again, lower the TTL values of the zone file a few days before the migration. This will decrease the caching time on other nameservers.

After the migration, increase the TTL values again to the old values.

The view times I was confronted with a situation like this I just introduced an alternative domain or subdomain during migration. for instance have your web server on the new domain configured to respond to both www. and www2.yourdomain.com (www.yourdomain.com being your main URL) BEFORE migration. On day X make your name server change for your main domain www.yourcomain.com and create a redirect on your old server to redirect users to www2.yourdomain.com.

Visitors will be directed to the new server no matter what, either to www.yourdomain.com if the name resolution already resolves to the new server, or to www2.yourdomain.com if not.

This should give you a clean switch without any overlap. Of course it is more configuration work.

There are other variations of the same concept, like migrating your old server to www2. a couple of days before the migration, and then make a clean switch to www.

I guess the TTL values is the more elegant way

A question on the TTL values. Are those values respected by all name servers or do providers sometimes apply their own expiration time limits?

welo

[Prasert]

A question on the TTL values. Are those values respected by all name servers or do providers sometimes apply their own expiration time limits?

RFC1537 gives recommendations for these values. In a static environment, using higher values will result in less traffic to your dns.

It's common practice that providers throughout the world will optimize their own dns records and trust other domains.

However, ISPs in Thailand are known to not follow these guidelines. Some ISPs use dns configurations that respond to (blocked) hostnames with a domestic IP address, showing a page that says access blocked. But any other host in the same domain will result in host-not-found, and further records are usually omitted as well.

So don't be surprised if Thai dns servers cache information longer than configured.