Same yet different?

[Jim Reid]

>>>>> "Dave" == Dave Nelson <dnelson at vnet.net> writes:

    Dave> We are using stub entries to share data between master
    Dave> nameservers on a private network.  I have gotten these error
    Dave> messages in my syslog:

    Dave> Oct 28 10:06:44 ns1 named-xfer[23180]: [198.235.216.137] not authoritative for anx.abc-tech.com, SOA query got rcode 0, aa 0, ancount 0, aucount 12

    Dave> Oct 28 10:06:44 ns1 named-xfer[23181]: [199.191.128.105] no SOA found for anx.cat.com, SOA query got rcode 3, aa 1, ancount 0, aucount 1

    Dave> Could someone explain the differences between these two messages?

The first one is that the name server at 198.235.216.137 is not
authoritative for the anx.abc-tech.com zone. Therefore named-xfer
has been unable to perform a zone transfer for that zone frm that name
server. The second means that the name server at 199.191.128.105 was
unable to find a SOA record for anx.cat.com.

The first problem is caused by sending zone transfers to a
non-authoritative name server. This can either be because the
masters{} statement in named.conf has the wrong IP addresses for the
anx.abc-tech.com zone or because something is broken on the name
server at 198.235.216.137. [Maybe it's not master or slave for the
zone or there are syntax errors in the zone file for anx.abc-tech.com
on that server.] The second problem is simple. You have tried to
transfer a non-existent zone! The name server on 199.191.128.105
cannot find a SOA record for anx.cat.com. In fact NO record type
appears to exist for this name - at least that's what ns1.cat.com, the
master server for cat.com, says - so anx.cat.com does not exist.