Snow Leopard: DNS broken after sleep?

[badsandwich]

just wanted to throw my oar in as well.
I’m using openDNS and that doesn’t help. I know it’s a mac problem because my windows laptop does not have any problems at all.
However I can’t say for certain what the cause of it is. I usually let my laptop sleep quite often so it may well be that shutting it down will help.
I also thought it might be happening when on battery power but there do seem to be cases where it happens on mains power.

I might try swapping out the router this weekend, just so i can rule that out.

Does anyone know if manually setting the IP and DNS in network config works, as someone mentioned above?

 

[hphoto]

I agree. This is truly annoying. I've got my own hack to kind of work around this problem. I created a cron job that will kill mDNSResponder every minute.

$ sudo crontab -e

then add this line:
* * * * * /usr/bin/killall mDNSResponder

Snow Leopard will still not resolve local hostnames sometimes, but at the top of every minute, the above cron job will kill mDNSResponder and it will resolve local hostnames. I hope this helps someone. I really hope Apple will fix this bug soon.

 

[gps]

I agree. This is truly annoying. I've got my own hack to kind of work around this problem. I created a cron job that will kill mDNSResponder every minute.

$ sudo crontab -e

then add this line:
* * * * * /usr/bin/killall mDNSResponder

Snow Leopard will still not resolve local hostnames sometimes, but at the top of every minute, the above cron job will kill mDNSResponder and it will resolve local hostnames. I hope this helps someone. I really hope Apple will fix this bug soon.

...mmh, not sure... this would kill also the active bonjour connections on local network... are u sure?

gp

 

[twgil]

Disk Error manifesting as DNS errors

I was having DNS problems with Snow Leopard and tried a ton of stuff to fix it. I finally got it fixed.

My problem had nothing to do with DNS. To find the problem, I ran a "verify disk" in Disk Utility and found a Invalid Sibling Link. I followed the instructions at http://www.macosxhints.com/article.php?story=20070204093925888. Basically, it says run fsck_hfs -r /dev/disk0s2 while booting from the install CD and unmounting the drive. I had to run fsck_hfs -f /dev/disk0s2 before the problem was fixed. The disk was successfully repaired, and I am back on the internets.

Even if you don't have a "Invalid Sibling Link" error but you do have some other error on the disk, try just doing a "repair disk" in Disk Utility.

I really hope this helps someone out.

 

[mercspeed]

$0.02:

I have static and DHCP wired networks, as well as .1x auth for a WLAN @ work and a wpa2 wlan @ home.

When @ work on wired lan, I have the exact same issue as others mentioned in the thread, where there is no ability to resolve DNS.

Currently the quickest two methods employed to circumvent the issue are to either change location from static to dhcp on the wire, or kill the airport and turn it on again.

I spend a lot of time using terminal.app so if I am there I usually flush the route table and re-add the DG, which resolves the issue also.

What I would like to state, is that for me, the issue is not purely related to a sleep event, but can happen any time, and completely randomly. It is particularly frustrating when trying to resolve local host names.

my MBP is a late 2009 17" 3.06 with all the bells & whistles, running latest 10.6.2

I must say, it is really <insert multiple expletives here> annoying.

 

[khooke]

I have a 2009 MPB with 10.6.4 installed.

I'm pretty sure my issue started after the last update to 10.6.4 but I'm not positive.

My symptoms are resolving addresses take forever, webpages load over my Wifi and DSL like we're on dialup, and when the issue starts happening it affects every other computer on my home network. If they are already powered on and surfing the web, as soon as I turn on my Mac they slow down to a crawl. It doesn't seem related to returning from a sleep. SOmetimes it happens immediately after a clean boot, sometimes it takes a few minutes.

I can solve it by disabling Airport, and then reenabling it again. Then I'll get a few minutes before it starts happening again. I noticed someone else said this was a temporary fix for their issues so thought I'd describe my problem too.

What I have noticed using Wireshark is when things start going slow, my Mac is spewing several
'Standard Query SOA local'
requests a second, followed by the reply:
'Standard query response, No such name'

This continues until I stop Airport and restart it. While the requests are being issued I get the slow internet response, when they stop I'm back to normal.

Any ideas?

 

[khooke]

Killing the mDNSResponder process also fixes the issue.

It always seems to happen straight from a cold boot and logon, or after waking from sleep. Disabling and enabling Airport a few times will also get it to stop although sometimes it takes several attempts before the "SOA local." lookups stop.

Hope Apple is reading this - would very much like a fix in the next update please!

 

[Michaelgtrusa]

Despite the dns patch after awake from sleep/random during the day I still get can't connect to sever messages.

 

[ndpitch]

Resurrecting this forum.

Lately I've been having very annoying intermittent airport issues. Ethernet is fine. Randomly, wireless will just come to a halt, and I have to restart airport to get it fixed, but the issue eventually returns. Airport never indicates the connection has dropped, though.

I just did a clean install of snow leopard, and I'm still having issues! I'm running the latest version of snow leopard as well.

For the record, it was always working fine, I've only noticed this cropping up in the last couple weeks or so. Is there anyone out there still having these issues on the latest snow leopard version?

Problem is localized to my MacBook pro, every other device on wireless is good to go.

 

[trackbikes]

. Is there anyone out there still having these issues on the latest snow leopard version?

Got these problems, with a wired connection on a 2011 iMac.

Come out of sleep and DNS doesn't work, quick restart and it works perfectly.

I have 4 dns entries listed 2 google public dns's and 2 from my ISP

 

[Marx55]

Got these problems, with a wired connection on a 2011 iMac.

Come out of sleep and DNS doesn't work, quick restart and it works perfectly.

I have 4 dns entries listed 2 google public dns's and 2 from my ISP

Same problem here on Mac OS X 10.6.8 after Mac sleep on wired Ethernet connection. How to fix it (besides restarting the Mac)?