kcd at chrysler.com
Tue Jun 10 14:21:27 UTC 2014
You're right: I misinterpreted "no name-server" as "no such host" (aka
NXDOMAIN), but actually your explanation makes more sense.
On 6/9/2014 6:07 PM, Barry Margolin wrote:
> In article <mailman.401.1402350461.26362.bind-users at lists.isc.org>,
> Kevin Darcy <kcd at chrysler.com> wrote:
>> That scenario still shouldn't have led to an NXDOMAIN. If none of the
>> delegated nameservers are responding, you'd get a timeout or SERVFAIL.
>> So I think there's still some investigation to be done. But using dig
>> instead of nslookup at least makes things clearer :-)
> Where did he say he got NXDOMAIN? He said he got "no name-server", which
> is not a dig error I've ever seen. Maybe he was abbreviating from "No
> nameserver could be reached", which is what dig says when it times out
> waiting for a reply.
More information about the bind-users