Transferred domain registration for mysite.com to namecheap last week, without issue, but did not change DNS at that time. Approximately 12 hours ago, I attempted to switch DNS to namecheap nameservers (a "simple" operation through namecheap panel) and then created A records to point to a different IP address than where the domain had pointed previously.
Checking propagation via whatsmydns.com, all records show mysite.com pointing to the new IP address, indicating to me that namecheaps DNS servers are working properly.
What's strange is that I cannot access the domain via a browser at mysite.com, it times out here from my desktop in Chicago (as an RCN broadband subscriber); "ping mysite.com" returns the old IP address and hangs, which is not a "correct" result vs. my expectations.
However, if I "curl mysite.com" while logged into servers at a NJ data center I get the expected response (and the output is the expected html ), and "ping mysite.com" looks correct showing the newly updated IP address that I'd expect. Lastly, if I ssh into the uChicago network and run ping or curl, I get the "proper"/expected response.
So, I'm thinking this is a classic DNS propagation issue. I know it's only been 12 hours, but I'm woefully inexperienced re:DNS and am now wondering if there's something I missed.
I'm content to wait it out a bit, but that's a little careless. So hopefully I've provided enough clues that someone smarter than me can either confirm that it looks like a DNS propagation issue, or can otherwise point me towards more ways to test for possible errors. Thanks.
Edit: Investigating this a little further, here is the output from dig mysite.com @a.root-servers.net":
Edit 2: polynomial pointed out that I failed to leave a space before the @, which gave incorrect results. I've updated the queries and here are the new results.
; <<>> DiG 9.6-ESV-R4 <<>> mysite.com @a.root-servers.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19132 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;mysite.com. IN A ;; AUTHORITY SECTION: com. 172800 IN NS j.gtld-servers.net. com. 172800 IN NS b.gtld-servers.net. com. 172800 IN NS i.gtld-servers.net. com. 172800 IN NS a.gtld-servers.net. com. 172800 IN NS c.gtld-servers.net. com. 172800 IN NS e.gtld-servers.net. com. 172800 IN NS l.gtld-servers.net. com. 172800 IN NS d.gtld-servers.net. com. 172800 IN NS m.gtld-servers.net. com. 172800 IN NS g.gtld-servers.net. com. 172800 IN NS f.gtld-servers.net. com. 172800 IN NS h.gtld-servers.net. com. 172800 IN NS k.gtld-servers.net. ;; ADDITIONAL SECTION: a.gtld-servers.net. 172800 IN A 22.214.171.124 a.gtld-servers.net. 172800 IN AAAA 2001:503:a83e::2:30 b.gtld-servers.net. 172800 IN A 126.96.36.199 b.gtld-servers.net. 172800 IN AAAA 2001:503:231d::2:30 c.gtld-servers.net. 172800 IN A 188.8.131.52 d.gtld-servers.net. 172800 IN A 184.108.40.206 e.gtld-servers.net. 172800 IN A 220.127.116.11 f.gtld-servers.net. 172800 IN A 18.104.22.168 g.gtld-servers.net. 172800 IN A 22.214.171.124 h.gtld-servers.net. 172800 IN A 126.96.36.199 i.gtld-servers.net. 172800 IN A 188.8.131.52 j.gtld-servers.net. 172800 IN A 184.108.40.206 k.gtld-servers.net. 172800 IN A 220.127.116.11 ;; Query time: 3 msec ;; SERVER: 18.104.22.168#53(22.214.171.124) ;; WHEN: Fri Oct 14 01:04:16 2011 ;; MSG SIZE rcvd: 497
And then from "dig mysite.com @dns1.registrar-servers.com" (that's a namecheap dns server):
; <<>> DiG 9.6-ESV-R4 <<>> mysite.com @dns1.registrar-servers.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55527 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;mysite.com. IN A ;; ANSWER SECTION: mysite.com. 1800 IN A [IP ADDRESS THAT IS CORRECT] ;; Query time: 31 msec ;; SERVER: 126.96.36.199#53(188.8.131.52) ;; WHEN: Fri Oct 14 01:07:09 2011 ;; MSG SIZE rcvd: 57