It's as if anything that tries to use the Mac's DNS, doesn't work, but the tools (DIG, NSLOOKUP, HOST) must use their own built in utilitiy to resolve DNS that is independant of the Mac DNS utility? My guess is the Mac's mDNSResponder is responsible for this, and that's why PING, Safari, Firefox, Twitterrific, etc, don't work. ![]() So not only does ping not work, but Safari/Chrome/Firefox no longer work. Then I tried NSLOOKUP and DIG, and they both work?!? Another weird side note is that I fired up my Windows in VMware, and Firefox/Ping both work when the network adapter is in NAT and Bridged mode. I get "ping: cannot resolve Unknown host". That's when I first started with ping from the terminal, and it didn't work. ![]() I have a MacBook running 10.6.4 and the Internet stopped working.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |