0

I have a split DNS situation happening. I have updated the DNS record on both local and public DNS servers.

nslookup recognizes that the A record has been updated:

user@MacBook-Pro:~ $ nslookup web01.peoplekeys.com
Server:     10.0.3.6
Address:    10.0.3.6#53

Name:   web01.peoplekeys.com
Address: 104.237.145.22

but then when I ping, it tries to use the old A record value.

user@MacBook-Pro:~ $ ping web01.peoplekeys.com
PING web01 (45.79.153.243): 56 data bytes
64 bytes from 45.79.153.243: icmp_seq=0 ttl=53 time=179.290 ms
64 bytes from 45.79.153.243: icmp_seq=1 ttl=53 time=179.189 ms

When I VPN outside of my internal network it is the same.

user@MacBook-Pro:~ $ nslookup web01.peoplekeys.com
Server:     209.222.18.222
Address:    209.222.18.222#53

Non-authoritative answer:
Name:   web01.peoplekeys.com
Address: 104.237.145.22

then with ping

user@MacBook-Pro:~ $ ping web01.peoplekeys.com
PING web01 (45.79.153.243): 56 data bytes
64 bytes from 45.79.153.243: icmp_seq=0 ttl=53 time=179.290 ms
64 bytes from 45.79.153.243: icmp_seq=1 ttl=53 time=179.189 ms

I have tried:

user@MacBook-Pro:~ $ sudo killall -HUP mDNSResponder
user@MacBook-Pro:~ $ sudo dscacheutil -flushcache

and it does not pull the updated DNS record. I would like to avoid specifying a hosts entry just to overcome this issue, but why would ping not respect this updated DNS entry?

  • Have you tried rebooting the Mac after entering the two commands (sudo killall ...)? Sometimes, I need to just restart the Macbook's WIFI instead of rebooting. Also if you happen to be on Yosemite, try sudo discoveryutil mdnsflushcache. – otter.pro Jul 14 at 3:55

You must log in to answer this question.

Browse other questions tagged .