I'm running on 10.8.2. All of a sudden, traditional nameserver lookups are failing on my machine:
$ nslookup www.att.com ;; connection timed out; no servers could be reached $ dig www.att.com ; <<>> DiG 9.8.3-P1 <<>> www.att.com ;; global options: +cmd ;; connection timed out; no servers could be reached
But operations that use name services work fine:
$ scutil -r www.att.com Reachable $ ping www.att.com PING e2318.dscb.akamaiedge.net (22.214.171.124): 56 data bytes 64 bytes from 126.96.36.199: icmp_seq=0 ttl=55 time=22.862 ms 64 bytes from 188.8.131.52: icmp_seq=1 ttl=55 time=26.947 ms ^C --- e2318.dscb.akamaiedge.net ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 22.862/24.904/26.947/2.043 ms
I've tried setting the name server addresses to different destinations via the
network system preference (e.g., 184.108.40.206, 220.127.116.11, 18.104.22.168, etc.) but that doesn't seem to make any difference.
I'm guessing there is an internal configuration file for the on-board DNS server that isn't getting updated, but I haven't a clue where to look for that.