I repointed the nameservers on Article Depot around 48 hours ago. Now within a few hours the site went to the new location at one of my offices (The home office to be exact). Now I have a different office about 10 miles away where it still resolves to the old address. Now I have cleared the DNS Cache through the command line but it still resoves to the old server. Is it possible it hasn't propogated fully yet or is there another possible culprit locally? Thanks
If I understand DNS etc. correctly, there are many places it can become cached and stay cached for longer than you hoped for. I just swapped servers and initiated it yesterday just after noon. Still not propagated (tried a lot of online proxy browsers, all old site).
So then I guess the question is what other people see while I wait for things to clear (more idea on how to clear them are welcomed) On the left hand side do you see an ad for Fathers Day (Green) or a Cute Teddy Bear? Cheers PS. The Fathers Day is the new site as I am waiting to change it when everything propogates.
Fathers day for me. Also try [search=google]surf proxy[/search] and see what others elsewhere in the world see.
Don't know if its coincidence or not but I used one of those surf proxies and now I can go directly to the updated site. (I couldn't 2 minutes ago) Its like it cleared something locally. Thanks for the help! PS. Guess its time to update Weirs Ad .. lol
Longest I've seen it take is 3 days, you can flush your own DNS servers if you're running them other than that you just have to sit it out.
It could be a couple of different things - 1) your computer has cached the address. I believe there's a dos command to clear it... maybe ipconfig /dnsflush or a net command. 2) your office dns cache has not updated if you run one. 3) your ISP dns cache has not updated. Sometimes it will take several days for ISP caches to update.
If your ISPs DNS caches for too long, you can always set your DNS to something else outside of your ISP.
You can check your name servers if you follow my instructions in the thread 15242. If you would like to see TTL (time to live) of the returned resource records, type set d2 in nslookup (Windows) or use dig on Linux: dig your-domain.com. +trace The number in the returned results will be TTL. All TTL values are in seconds. J.D.