July 15th, 2011, 11:01 AM
Changing Hosts...taking too long?
I few days ago, I copied the files from my site to a new webhost, edited a few files, and changed the nameserver information on my domain manager. One computer/connection I use pulls up the new version, but another computer/connection is STILL pulling up the old site. Yesterday I discovered that I had mistyped the first of 5 nameservers for my new host, and promptly fixed it. I've tried clearing the caches of all my browsers and reloading the site, even told the browser not to predict network actions, but it's not helping.
Is it possible that it is still updated through the internet or is the one computer hiding the connection information somewhere?
I don't want to delete the files from the old host until I'm sure that people are all being directed to the new site.
Thanks for any ideas.
July 15th, 2011, 01:45 PM
Its possible that you are receiving cached DNS records from your nameserver, probably due to a high TTL.
Use dig (on Linux), nslookup (on Windows) or a web tool like dnsstuff to check if the DNS resource records are what you are expecting.
July 15th, 2011, 02:21 PM
I'm using windows. I've never used nslookup. How would I go about using it?
Originally Posted by Eddie_D
July 15th, 2011, 04:30 PM
Open up the command prompt and type nslookup. You'll get the ">" prompt next. Just type in the domain name and it will by default pull the A record from the server.
For more info:
July 15th, 2011, 05:06 PM
Ok, when I do that, it returns my old host's ip. Is there a way to resolve this? I'm suspecting that it's an issue on this computer...
Maybe if I just don't ping that site for a few days it will reset the TTL?
July 15th, 2011, 05:52 PM
Doesn't matter. TTL's count down regardless. Only way it will be an issue is if the name servers are still giving out the old IP. Try to do this:
This should show you the TTL's the server has.