SUMMARY: DNS non-authoritative response

John Malick (john@starinc.com)
Thu, 05 Mar 1998 16:38:29 -0500

The error that caused non-authoritative results, even though I was a primary
server, was in my main zone file. I had an MX record but mistakenly missed
the priority number, i.e. 10, 20, etc., that is part of the MX record. This
one line entry seemed to cause the entire domain to fail in terms of the
authoritative nature.

Rather bogus but its fixed.

Thanks all to those you led me to the zone file.

------------------------------------------------

Original message below:

> Running Solaris 2.5.1 with the version of BIND that ships with it.
>
> We are a primary DNS server for our domain aaa.net.
>
> Whenever a lookup is performed to host.aaa.net with nslookup, a response
> comes back with the header Non-authoritative answer:
>
> This is causing some problems with an application we have that expects
> the response to be authoritative. Of course, since we are the primary
> server for our own domain, we should be getting an authoritative response.
>
> Any reasons why we would be getting a Non-authoritative answer from nslookup?