Mac not handling DNS but a windows box on the same network is :(

Hi everyone,

So I'm sitting in a hotel room in Shanghai with my mac (running snow leopard) and unfortunately I'm using an instance of Windows XP running under VMWare Fusion to access the web. The windows instance is using bridged networking-so it has it's own IP address. I can access web pages without problems (other than using internet explorer makes me want to tear my hair out).

My mac does have an (non-self-assigned) IP address, and it seems to have two DNS servers listed - and I can ping them without any issues. As long as I use IP addresses I can even talk to things out on the network (I can ssh to a box that I have back in the states for example). And yet if I try to open a web page in Safari, I get "Safari can’t open the page “<url>” because your computer isn’t connected to the Internet.".

Two things to note: Network Diagnostics is showing green for "Network Status", "Network Settings", "ISP" - and red for "Internet" and "Server". Also, when I use the command line tool "nslookup" I can successfully lookup the IP address of a name. However the man-page of nslookup warns: "The nslookup command does not use the host name and address resolution or the DNS query routing mechanisms used by other processes running on Mac OS X.".

Any ideas would be appreciated, because this brief foray back into Windoze is making me queezy.

Thanks

Air and 15" MBP and iPhone 3GS, and an Apple TV, Mac OS X (10.6)

Posted on Sep 11, 2009 12:25 AM

Reply
19 replies

Sep 13, 2009 4:27 PM in response to Snoop Dogg

Hi Snoop - I left it running for quite a while and it didn't seem to end. But here's what it came up with so far (as you can see it had been running for 13 minutes at this point):

Timestamp A/R Flags if Name T C Rdata
18:12:44.864 Add 2 0 www.apple.com. 1 1 No Such Record
18:13:21.202 Add 3 0 www.apple.com. 5 1 www.apple.com.akadns.net.
18:13:21.202 Add 2 0 www.apple.com.akadns.net. 1 1 17.149.160.10
18:14:39.571 Rmv 1 0 www.apple.com.akadns.net. 1 1 17.149.160.10
18:14:39.571 Add 2 0 www.apple.com.akadns.net. 1 1 No Such Record
18:25:09.377 Add 2 0 www.apple.com.akadns.net. 1 1 17.149.160.10

Interesting....

Sep 13, 2009 5:13 PM in response to paulsorensen

Yes, interesting. This definitely shows a problem. At 18:12:44.864 and 18:14:39.571, it said www.apple.com didn't exist. In order to figure this out, we'll need to see the responses from the DNS server, but this is going to log a lot of stuff.

Run all these Terminal commands, back to back to back...

*sudo killall -USR2 mDNSResponder*
*sudo killall -HUP mDNSResponder*
*dns-sd -Q www.apple.com*

Then wait for the last Terminal command to show *No Such Record*. Then use the Console application and select *Open System Log* from the File menu to view the system.log, and type mDNSResponder in the search field so you can filter on just the logs from mDNSResponder. It will have logged all the DNS queries and responses. Look for the timestamp of the No Such Record log from the Terminal command and find that same time in system.log. Then look for queries and responses for www.apple.com. Try to post the queries and responses to the board.

Sep 14, 2009 12:12 AM in response to Snoop Dogg

Here's one that worked (and one that didnt will follow):

Sep 14 02:01:30: --- last message repeated 233 times ---
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: -- Sent UDP DNS Query (flags 0100) RCODE: NoErr (0) RD ID: 16942 45 bytes from port 53630 to 211.167.97.67:53 --
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 1 Questions
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 b. dns-sd.udp.0.3.168.192.in-addr.arpa. PTR
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Answers
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Authorities
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Additionals
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: --------------
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: -- Received UDP DNS Response (flags 8182) RCODE: ServFail (2) RD RA ID: 16942 45 bytes from 211.167.97.67:53 to 192.168.3.110:53630 --
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 1 Questions
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 b. dns-sd.udp.0.3.168.192.in-addr.arpa. PTR
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Answers
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Authorities
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Additionals
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: --------------
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: -- Sent UDP DNS Query (flags 0100) RCODE: NoErr (0) RD ID: 7974 30 bytes from port 56898 to 211.167.97.67:53 --
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 1 Questions
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 www.apple.com.akadns.net. Addr
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Answers
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Authorities
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Additionals
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: --------------
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: -- Received UDP DNS Response (flags 8180) RCODE: NoErr (0) RD RA ID: 7974 364 bytes from 211.167.97.67:53 to 192.168.3.110:56898 --
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 1 Questions
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 www.apple.com.akadns.net. Addr
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 1 Answers
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 TTL 18 4 www.apple.com.akadns.net. Addr 17.149.160.10
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 9 Authorities
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 TTL 10126 18 akadns.net. NS asia9.akadns.net.
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 1 TTL 10126 17 akadns.net. NS eur1.akadns.net.
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 2 TTL 10126 17 akadns.net. NS use3.akadns.net.
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 3 TTL 10126 15 akadns.net. NS zb.akadns.org.
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 4 TTL 10126 17 akadns.net. NS usw2.akadns.net.
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 5 TTL 10126 17 akadns.net. NS use4.akadns.net.
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 6 TTL 10126 15 akadns.net. NS zd.akadns.org.
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 7 TTL 10126 15 akadns.net. NS zc.akadns.org.
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 8 TTL 10126 15 akadns.net. NS za.akadns.org.
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 9 Additionals
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 TTL 105625 4 asia9.akadns.net. Addr 220.73.220.4
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 1 TTL 23728 4 eur1.akadns.net. Addr 195.59.44.134
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 2 TTL 33071 4 use3.akadns.net. Addr 204.2.178.133
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 3 TTL 137479 4 use4.akadns.net. Addr 208.44.108.137
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 4 TTL 100246 4 usw2.akadns.net. Addr 12.183.125.5
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 5 TTL 11016 4 za.akadns.org. Addr 213.254.204.197
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 6 TTL 11016 4 zb.akadns.org. Addr 12.183.125.5
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 7 TTL 11016 4 zc.akadns.org. Addr 124.40.52.133
Sep 14 02:01:30 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 8 TTL 11016 4 zd.akadns.org. Addr 204.2.178.133

Here's the one that responded with "No Such Record":

Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: -- Sent UDP DNS Query (flags 0100) RCODE: NoErr (0) RD ID: 7974 30 bytes from port 56898 to 211.167.97.68:53 --
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 1 Questions
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 www.apple.com.akadns.net. Addr
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Answers
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Authorities
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Additionals
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: --------------
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: -- Received UDP DNS Response (flags 8100) RCODE: NoErr (0) RD ID: 7974 238 bytes from 211.167.97.68:53 to 192.168.3.110:56898 --
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 1 Questions
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 www.apple.com.akadns.net. Addr
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Answers
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 13 Authorities
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 TTL1879048 20 . NS L.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 1 TTL1879048 20 . NS M.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 2 TTL1879048 20 . NS A.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 3 TTL1879048 20 . NS B.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 4 TTL1879048 20 . NS C.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 5 TTL1879048 20 . NS D.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 6 TTL1879048 20 . NS E.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 7 TTL1879048 20 . NS F.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 8 TTL1879048 20 . NS G.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 9 TTL1879048 20 . NS H.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 10 TTL1879048 20 . NS I.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 11 TTL1879048 20 . NS J.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 12 TTL1879048 20 . NS K.ROOT-SERVERS.net.
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: 0 Additionals
Sep 14 02:03:32 wai-bun-katie-wongs-macbook-pro mDNSResponder[32]: --------------

Sep 14, 2009 12:54 AM in response to paulsorensen

Ok - so the afternoon before I head back to the United States I got it working - thanks to everyone who answered!

So if Apple is watching, the way that I fixed the problem (after the diagnostic help of the oher folks on the thread) was to override the DNS settings to remove the bad DNS. It looks like the mac was hitting up the bad DNS every time but windows is (either by luck or by design) hitting up the good one.

Thanks everybody.

Sep 14, 2009 7:20 AM in response to paulsorensen

That could be a result of the bug/feature I've asked Apple about but have yet to receive a response for.

Windows and Mac OS X Leopard will use manually-specified DNS servers in the order they were provided.

However for some reason, Snow Leopard occasionally reverses the order.

Thus if the working server was the first on the list, that would explain why Windows always worked and the Mac worked sometimes (or never.)

Sep 14, 2009 10:27 AM in response to Dogcow-Moof

Glad you were able to get it working......

I've had a similar problem with no solution..

On my LAN, there is an audio box connected to our LAN. It has a static IP address, but I can't reach it via Safari in Mac OS, but can reach it via Ubuntu or XP running under parallels on the same machine. I am using the IP address of the box to talk to it.

It's been like this for years, and the only reason I set up Ubuntu was to access this one box.

I don't understand how the Mac misses the box but the other OS's running in emulation can always reach it... Even this Mac booted natively in Ubuntu or XP can reach the box, so there is something in the way Mac OSX looks for it that doesn't allow it to find it.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Mac not handling DNS but a windows box on the same network is :(

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.