Q: Why don't ping and nslookup agree after server migration?
Our domain, seattlepeacechorus.org, running Wordpress, was migrated two weeks ago from one host server, mongoose.arvixe.com, to another, dallas138.arvixeshared.com.
I have two mac laptops and during the migration I upgraded my main laptop to El Capitan. The old laptop runs OS 10.6.8.
Since then, http://seattlepeacechorus.org does not work in any browser on my main laptop, but works fine on the old laptop.
Subsequently, I have ruled out various causes.
1. It's not Wordpress. A simple HTML file FTPed to the server loads fine on the old laptop, but not on the new laptop.
2. It's not my DNS cache. I have run commands to clear the cache (sudo dscacheutil -flushcache;sudo killall -HUP mDNSResponder;say cache flushed) with variously configured DNS servers. No effect on the problem.
Curiously, ping and (I assume) my browsers continue to query mongoose, the old host server, at 198.58.93.2. However, nslookup finds the new server, dallas138, at 143.95.253.117. How can I fix my laptop so that the browser and ping find the correct server? Thank you.
Toms-Laptop-2:~ tom$ ping -o seattlepeacechorus.org
PING seattlepeacechorus.org (198.58.93.2): 56 data bytes
64 bytes from 198.58.93.2: icmp_seq=0 ttl=55 time=86.508 ms
--- seattlepeacechorus.org ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 86.508/86.508/86.508/0.000 ms
Toms-Laptop-2:~ tom$ nslookup 198.58.93.2
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
2.93.58.198.in-addr.arpa name = stats.mongoose.arvixe.com.
Authoritative answers can be found from:
Toms-Laptop-2:~ tom$ nslookup seattlepeacechorus.org
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: seattlepeacechorus.org
Address: 143.95.253.117
MacBook Air, OS X El Capitan (10.11)
Posted on Oct 20, 2015 2:18 PM