DNS and moving hosts

Hi guyz,
I am moving my website http://www.biologyformhtcet.com

Yesterday, I have changed the name servers of the domain to the new ones.
Today morning I found that the domain was pointing to its new host. But now its pointing again to its previous host.

Considering that it not even 24 hrs after I have changes the name servers, should I relax and wait for another 24 hrs?

Please suggest.
Thank you

 

from my end it points to 74.86.90.81 (and from nettools nslookup for example) though from domain name whois (http://whois.domaintools.com/biologyformhtcet.com) it points to 75.126.189.228 . This probably means that DNS update/propagation is not yet completed. Probably...

 

FYI DomainTools caches its IPs - good for historical reasons, but not for checking propagation.

 

Thanks Pr0t0n and Jay

 

It can flop back and forth until propagation is complete.

 

Thanks a lot. Even today early morning, it was pointing to the new IP, but later its pointing back to its old IP.

UPDATE: I just checked now and its pointing to its new location.(it wasn't few minutes ago). Lets hope that it won't fall back again ray:


Is this a problem: Now, the ping tool points to the new IP address, but still if I try to visit the website, it takes me to the old host. should I worry or just be patient?

Thanks for your time.

 

chill and sip some cold coffee, it should be working properly by now.

 

I wouldn't worry about that. That could just be a local issue, where your PC hasn't cleared out the cache yet. I had two PCs side by side on the same internet connection, and when I changed a site, one PC showed the new host, and the other showed the old host. It took a day or two, but it finally sorted itself out.

 

Hi,

You can confirm if the delegation actually changed at the gtld name-servers by doing the following:

This checks a gtld server what name-servers are authoritative for the domain

$ dig +short @F.GTLD-SERVERS.NET. NS biologyformhtcet.com.
ns1.techiehost.org.
ns2.techiehost.org.

This checks that the name-servers know they are authoritative for the domain and are serving the correct records.

$ dig +short @ns1.techiehost.org. NS biologyformhtcet.com.
ns1.techiehost.org.
ns2.techiehost.org.

dig +short @ns2.techiehost.org. NS biologyformhtcet.com.
ns1.techiehost.org.
ns2.techiehost.org.

In short, it's just a caching issue. Clear your resolver cache and your browser cache and try again.

 

While testing these things, the following tips may come in handy:

* In Windows, you can flush your DNS cache at the command prompt using ipconfig /flushdns

* If you use OpenDNS as your DNS provider while cruising around the web, there's a place on their site where you can force a cache refresh for a particular domain.