15

I can't reach websites using browsers in OS X 10.6.7 on a MacBook Pro, possibly after resuming from sleep. I've had this problem before and it has been solved by a reboot, but I since I got it again I wanted to get to the root of it.

It all starts with Chrome and Safari not being able to browse the Internet. Here's a list of what works and what doesn't:

Doesn't work

  • Browse Internet in Safari, Chrome and Firefox ("You are not connected to the Internet.")
  • Adium

Works

  • ping google.com
  • wget google.com
  • curl http://www.google.com
  • traceroute google.com
  • nslookup google.com
  • Browse Internet in any browser with the Charles proxy started
  • Browse 74.125.39.103 (Google IP) in any browser
  • Skype

I haven't configured any proxy at all (except for when running with Charles). Other computers on the network can reach Internet just fine. I'm connected to either Ethernet, the AirPort, or both but no combination makes a difference.

I've also tried to use a different DNS provider, Google Public DNS, but that didn't work either (nslookup, ping etc used the new name server without problems).

Visiting the IP number of google.com in the browser works as stated above, and considering ping et al works, it seems to be a DNS issue? What could be causing this?

Improve this question
1
  • Have you tried using firefox? I mean it could be webkit but that's just another suggestions.
    – Muhammad Usman
    Commented May 11, 2011 at 8:00

4 Answers 4

Reset to default
9

Problem temporarily solved by running:

sudo killall mDNSResponder

As per this question: MacBook can't use internet, but nslookup and ping both work.

Still doesn't explain why this breaks down on sleep/resume though.

Improve this answer
2

Perform all these steps, checking after each whether the problem is resolved.

  1. Reboot your router

  2. Reset your Mac's PRAM

  3. In Terminal

    dscacheutil -flushcache

  4. In System Preferences/Network, create a new (non-duplicate) network location, and configure it for your needs

  5. In Terminal

    sudo launchctl unload /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist

  6. Patch the 4 mDNS system files back to 10.6.4

    See https://discussions.apple.com/message/12683257#12683257

    There is even a package with the files.

    In this post https://discussions.apple.com/message/13346662#13346662 he says that he is using the patch on 10.6.7.

    Nevertheless, backup your 10.6.7 files first.

    And confirm successful replacement of each file.

Improve this answer
3
  • I'm running on Lion, and my mDNSResponder isn't crashing at all. That seems to be the issue the poster of that question was describing
    – Yuval
    Commented Nov 1, 2011 at 5:40
  • can you post results of scutil --dns ?
    – freebairn
    Commented Nov 1, 2011 at 11:07
  • Thanks for your response! Here ya go: gist.github.com/1338535 What do you think?
    – Yuval
    Commented Nov 4, 2011 at 2:34
0

From OS 10.6 - Snow Leopard keeps dropping DNS :

I recently switched to a Mac running 10.6.latest as my primary machine and ran into this exact problem. I have a LAN-based DNS server to provide addresses for the other machines on the internal network and two DNS servers provided by my ISP. Intermittently, Firefox would fail to resolve the name of an internal server.

After some searching, I found this page that suggests Apple changed the way DNS servers are queried in Snow Leopard : Changes in DNS resolution in Mac OS X.

I found this article and made the suggested changes: OS X 10.6.3 and DNS server priority changes.

I hope this helps someone else get Snow Leopard to honor DNS server ordering instead of randomizing them.

Improve this answer
0

If sudo killall mDNSResponder temporarily solves it, then you could create an Applescript to run when you resume the computer from sleep.

Try creating a new user on your computer and see if it works in that.

Phone up Apple - http://www.apple.com/support/contact/.

Improve this answer
4
  • The user offering the bounty wrote that the accepted solution did not work for him.
    – Daniel Beck ♦
    Commented Oct 26, 2011 at 14:10
  • @DanielBeck Sorry. I have crossed it out.
    – gadgetmo
    Commented Oct 26, 2011 at 14:30
  • Thanks guys. Neither a new user nor does killing mDNSResponder works. All Apple gave me was the typical airport debugging advice, which didn't help at all. Any other ideas?
    – Yuval
    Commented Oct 27, 2011 at 5:59
  • I think this is worth noting, though: Charles Proxy does work. I have no idea why. If we can figure out what it is doing then maybe we can replicate it without using the program? I don't think it uses an actual proxy, but it somehow redirects the request to the localhost, which makes it work. Unless that is, that I'm wrong. Any ideas?
    – Yuval
    Commented Oct 27, 2011 at 6:00

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .