frederick t

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

Close

Q: Why don't ping and nslookup agree after server migration?

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Oct 20, 2015 8:54 PM in response to frederick t
    Level 10 (208,000 points)
    Applications
    Oct 20, 2015 8:54 PM in response to frederick t

    It looks like you may have edited the hosts file, and also the A and PTR DNS records don't match.

  • by frederick t,

    frederick t frederick t Oct 20, 2015 9:18 PM in response to Linc Davis
    Level 1 (0 points)
    Oct 20, 2015 9:18 PM in response to Linc Davis

    Thank you for responding. I appreciate your observations.

     

    (1) Yes! It turns out that I had edited my own /etc/hosts file and had forgotten about that. It was when we were in the process of setting up seattlepeacechorus.org and the domain registration had not completed. Now I have deleted the lines specifying the old IP address for the domain. Subsequently, ping and traceroute go to the right place, and my browser can open seattlepeacechorus.org pages. I am grateful for your help!

     

    (2) I opened the Advanced DNS Zone Editor from the cpanel for seattlepeacechorus.org, but it doesn't show a PTR record. Whereas I can see that the TXT and SRV records still reference the old server (mongoose), I have opened a ticket to have arvixe service fix them or advise me how to do that.