Since updating to 10.6.5 (via the combo update), I experience strange DNS problems on my laptop.
After working fine for some time, suddenly no DNS names are resolved any longer.
Looks like mDNSResponder simply died.
- This happens simultaneously in Firefox, Safari & even from the Terminal.
- It happens both on ethernet, and on wifi.
- I can still Ping my DNS servers, and I can ping my machine from remote as well.
- Everything where I can still remember the IP address seem to work fine.
- Problem happened in different networks
- Nothing obvious in the console messages
It really looks like a pure DNS problem, not a network issue.
Even the Windows emulation I sometimes run on that machine keeps working and can still resolve DNS names correctly.
I repaired permissions, reinstalled the update, cleared the DNS cache... the usual.
Until now, nothing solved the problem. I need to reboot, to get dns lookup back.
This will then work for some time (in the order of hours) and suddenly I'm stuck again.
Most of what the guys are reporting I'm going through using 10.6.5 with DNS issue. What's interesting is that I was repairing permissions two days in a row, and the second time I got lots of lines corrected as well. How this is possible if nothing is installed in between?
Would it be possible that the recent Java upgrade has to do something with it?
Ten minutes after posting the above, I decided to repair permissions on a MacBook that was not shut down between permission repairs. The result is full of Java lines:
*Repairing permissions for “Snow HD”*
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jconsole.ja r", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jconsole.ja r".
User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib", should be 0, user is 95.
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib".
User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries", should be 0, user is 95.
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries".
Permissions differ on "System/Library/Java/Support/Deploy.bundle/Contents/Resources/JavaPluginCocoa.b undle/Contents/Resources/Java/deploy.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/Support/Deploy.bundle/Contents/Resources/JavaPluginCocoa.b undle/Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ".
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib", should be 95, user is 0.
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib".
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Libraries", should be 95, user is 0.
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Libraries".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib", should be -rwxr-xr-x , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib".
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
*Permissions repair complete*
I had odd DNS behavior in that Chrome and Safari would not work but Firefox would and it was just after the 10.6.5 upgrade, but I didn't associate it until I started digging around and found this thread. Traceroutes and nslookups were not affected. I reset my router, flushed DNS caches, refreshed IP on the router, manually edited the DNS settings in System Prefs and all kinds of things.
But when I finally read here that a PRAM/NVRAM reset might fix it, I recalled when that resolved a MacBook Pro networking/DNS odd issue I had previously, so I figured it might just work on my iMac. Sure enough, the reset was all it took to resolve my DNS issues. For my machine, that was accomplished by holding down Command-Option-P-R when starting up (after a shutdown), and letting go after the second chime. It's certainly worth a try for the other posters having similar issues!
Really painful, since we tried to resolve it with the cable company, we even returned a new router. I realized it is only showing up on mobile machines (wireless connections) so far. But this could be a coincidence as well.
Scuse me, I believe that only four out of eleven recurring permission repairs are addressed by the Apple Support Knowledgebase article that you referenced. If those errors were already known before the 10.6.5 release, wouldn't it have made more sense for Apple to have included a patch to stop them from reappearing, rather than maintaining an "ignore our errors" list, which seems to be growing like mushrooms under logs after it rains?
Got the same issue here, here are some details :
* I think I don't have the issue at home, where I use my ISP provided DNS servers (I have to send more time there though to be sure)
* I notice the issue at work, where we use a windows domain controler's DNS as cache (and resolver for internal PCs)
* Some domains don't resolve randomly, for example on an ebay listing page I have missing images, when clicking on some links they seem to not display
* Doing a DNS flush in a nearby terminal solves the issue temporarly, just after doing it (dscacheutil -flushcache) domains resolve again (I suppose the error gets cached, and doing this makes the resolver do a retry)
admanb wrote:
I had odd DNS behavior in that Chrome and Safari would not work but Firefox would and it was just after the 10.6.5 upgrade, but I didn't associate it until I started digging around and found this thread. Traceroutes and nslookups were not affected.
But when I finally read here that a PRAM/NVRAM reset might fix it
i had bad bad dns skipping addresses even google! so i switched to google dns - easy to remember - 8.8.8.8 - 8.8.4.4 - restart router and computer after change. firefox sped up a lot.
I have the same problem as initially described and further characterized by mseiden.
The following do not help:
1. sudo killall mDNSResponder
2. reset PRAM/NVRAM
3. change or restart network interface
4. turning off the firewall and Little Snitch
5. flushing the DNS cache: dscacheutil -flushcache
Things suggested to me that I have not yet tried:
1. wipe out /Library/Preferences/SystemConfiguration
2. manually set DNS to use Google DNS entries
- don't expect this to do anything since the problem occurs on different networks
3. disable IPv6
4. reinstall 10.6.5 update from combo updater
5. reinstall OS
One thing I noticed is that mDNSResponder appears to normally run with "Ss" state ("sleeping for less than 20 seconds") and when DNS dies the mDNSResponder state changes to "Us" ("process in uninterruptible wait"). I think the killall didn't actually kill the process. Next time I will try using kill -9.
levytv wrote:
i had bad bad dns skipping addresses even google! so i switched to google dns - easy to remember - 8.8.8.8 - 8.8.4.4 - restart router and computer after change. firefox sped up a lot.
This problem has nothing to do with the DNS provider -- DNS is working fine, except for the Apple libraries in 10.6.5. Non-Apple programs on the system have no trouble with DNS. Unfortunately, I like using Safari, Mail.app, Dashboard, MobileMe/Bonjour, etc. The bug is almost certainly related to the 10.6.5 changes for IPv6. Nothing is wrong with the network itself nor with the DNS provider. (I use Google's DNS resolvers also.)
In my work place, the DNS server usually set host cname. +For e.g. webmail (cname) for test.com domain.+ Now I've removed the +webmail (cname)+ and replace it with +webmail (host)+. This works!
It sounds like there's a couple of different things going on here.
In my case, I had the issue where we had www.companyname.com as a CNAME to www.companyname.local. www.companyname.local is a A record.
This worked fine on previous versions of OS X, and according to my read of the Bonjour documentation this should be working.
After 10.6.5 it stopped working. I just deleted the CNAME record on www.companyname.com, and replaced it with an A record that duplicates the .local record. After a dscacheutil -flushdns, the domain is resolving correctly.
In addition to my posting above, I've now tried:
1. reinstalling 10.6.5 from the combo updater
2. disabling IPv6
3. kill -9 mDNSResponder
I'm still convinced this is a problem with mDNSResponder. Just no idea why or how to reset the process without rebooting. I can't seem to kill the process with either "killall" (doesn't do anything) or "kill -9" (changes the process state from "Us" to "??").
Anyone able to fix the problem as originally stated (ie not the CNAME problem)? I've now seen this problem on 3 very different wireless networks and 1 wired network.
I also believe it is mDNSResponder (and that the bug is related to some IPv6 changes that Apple admits to doing in this release). It seems to be triggered when the system sleeps. I changed my power management settings to never sleep the CPU (just allow sleep for the disks and display), and I had Wake On Ethernet turned on already. Before I did that, the bug happened every time it slept. Since I changed it, the bug has not happened.
I think that sending mDNSResponder a USR1 might also reset it, once the bug happens. I know that worked at least once for me. Certainly changing the network configuration (e.g. re-plugging the Ethernet cable) will reset it.