not authoritative message error(new user)

[Kevin Darcy]

Samuel Sumner wrote:

> Just recieved a new /22 for the network, but when trying to update the
> secondary name servers I get this message concerning the new ip blocks:
>
> Jun 28 13:07:11 ns2 named-xfer[4319]: [205.165.40.2] not authoritative for
> 248.104.63.in-addr.arpa, SOA query got rcode 0, aa 0, ancount 0, aucount 2
>
> can anyone tell me what is going wrong here?

This is usually caused by a syntax error in the master file. named will load
the file (as best it can), but will only give out non-authoritative answers
for the zone. And then this non-authoritativeness causes the zone transfer
mechanism to fail. This is a feature, not a bug: it raises the visibility of
the problem to the point where it is likely to be fixed. Look in the logs on
the master to see what the problem is.


- Kevin