I recently had a similar network problem and it was driving me mad for days trying to figure out what went wrong.
The scenario was usually that whatever you type in Safari didn't work but you could ping it and NSLoopup answered everything correctly. /etc/resolv.conf was also showing the correct values and no proxy was involved, no NAT or anything else. Reinstalling 10.10 did not help. It usually happened when I brought my laptop home but it only happened on one of my laptops. I found some forum post which was tying such an issue to the default search domain. If you have TCP/IP configured to have your search domain set by DHCP it was fine but if you added it manually as well then it screwed up. So what OS X did is when you typed www.apple.com it was looking up www.apple.com.yoursearchdomain first and then failed immediately. This seems however only to apply if you enter the domain by hand, not when its handed out by DHCP. Since I removed my entry, my problems are gone. Another solution would be to run your own DNS caching server on localhost.That should also speed up your DNS queries. > > On 08 Jan 2015, at 08:46, Quinn The Eskimo! <[email protected]> wrote: > > > On 7 Jan 2015, at 16:38, Stéphane Sudre <[email protected]> wrote: > >> Also if you were to perform a nslookup (from the Terminal) query during that >> time with the same hosts' names, it would work fine. > > I'm not sure what point you're tying to make with this test but I wanted to > specifically call out that nslookup does not use the system DNS; it talks to > a DNS server directly. Thus, it's very common for nslookup to behave very > differently than standard DNS clients. A trivial example of this is: > > $ nslookup fluffy.local. > Server: 192.168.1.254 > Address: 192.168.1.254#53 > > ** server can't find fluffy.local.: NXDOMAIN > > $ ping fluffy.local. > PING fluffy.local (192.168.1.39): 56 data bytes > [...] > > The system tries to ensure that nslookup uses a reasonable DNS server by > default, but that's not always possible. > > So, nslookup is a good way to test your DNS server, and your connectivity to > that server, but it's not useful for testing the system DNS. > > Share and Enjoy > -- > Quinn "The Eskimo!" <http://www.apple.com/developer/> > Apple Developer Relations, Developer Technical Support, Core OS/Hardware > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Macnetworkprog mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/macnetworkprog/afink%40list.fink.org > > This email sent to [email protected]
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to [email protected]
