DNS Question...HELP..

[Jim Reid]

>>>>> "Joe" == Joe Weiss <joe at be-secure.com> writes:

    Joe> Suddenly my secondary name server has stopped updating the
    Joe> in-addr.arpa file from my primary name server.  All other dns
    Joe> files are being sent with no problems.  The error in my
    Joe> syslog on my secondary name server is as follows: (domain
    Joe> names and IP's have been carefully sanitized)

You shouldn't hide information like IP addresses and host/domain names
that might help someone - a volunteer remember! - diagnose your
problem. For example, they could query the actual name server that's
thought to be broken...

    Joe> Dec 22 11:08:21 ns2.my.domain named-xfer[26819]: [192.168.1.132] not authoritative for 1.168.192.in-addr.arpa, SOA query got rcode 0, aa 0, ancount 1, aucount 0

The log message explains the problem. The name server on 192.168.1.132
is not authoritative for the 1.168.192.in-addr.arpa zone. Therefore
it's not possible to perform zone transfers of 1.168.192.in-addr.arpa
from that server. The reason why this name server isn't authoritative
for the zone can only be guessed at because you chose to conceal the
relevant information.

There are three possibilities. [1] 192.168.1.132 is not configured as
a master or slave server for this zone. [2] The name server on
192.168.1.13 failed to load this zone because of syntax errors in the
zone file. [3] This name server is a slave for 1.168.192.in-addr.arpa
and it can't get a copy of the zone from the zone's master server.
Consult the log files and named.conf on 192.168.1.132 to find out
which one of these three possibilities is the cause.