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/archive%40mail-archive.com This email sent to [email protected]
