Look for messages from launchd or mDNSResponder that may indicate why mDNSResponder is having problems launching and staying running. Use the Console utility ( /Applications/Utilities/Console.app), hit the "Show Log List" button and select the "All Messages" log stream. Update: If the above commands don't work (and note that everything in them is case-sensitive), then mDNSResponder probably isn't running, or is crashing or otherwise exiting prematurely at every launch. I've seen mDNSResponder fail to unstick itself with just a HUP. NB: Don't just HUP it, really kill it and let launchd automatically restart it. If dns-sd can't resolve host names but traditional Unix tools like nslookup/ dig/ host can, then the mDNSResponder daemon is probably horked and needs to be restarted: sudo killall mDNSResponder Did I understand from the comments that nslookup works even when your Mac is still set to use your router's DNS proxy at 192.168.1.1? If so, then see if Mac OS X's other DNS resolver codepath works, by doing a DNS query with the dns-sd tool: dns-sd -Q (You'll have to Ctrl-C out of this command once you get results or decide to give up)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |