Not Authoritative For.....

Lisa Casey lisa at jellico.net
Tue Jul 23 18:52:28 UTC 2002




 Hi Folks,

 I have two name servers, one of which (65.207.130.4) is primary for a bunch
of domains, the other is secondary for those domains. I'm getting this error
message on the secondary server for two of my reverse  files:

Jul 23 18:10:19 bluegrass named[126]: Ready to answer queries.
Jul 23 18:10:20 bluegrass named[126]: Err/TO getting serial# for
"131.207.65.in-addr.arpa"
 Jul 23 18:10:20 bluegrass named[126]: Err/TO getting serial# for
 "63.171.176.in-addr.arpa"
 Jul 23 18:10:20 bluegrass named-xfer[3477]: [65.207.130.4] not
authoritative
 for 131.207.65.in-addr.arpa, SOA query got rcode 0, aa 0, ancount 0,
aucount
 2
 Jul 23 18:10:20 bluegrass named-xfer[3478]: [65.207.130.4] not
authoritative
 for 63.171


 I did a Google search of this newsgroup looking for a solution, but all of
 the answers that I saw said to look in the log file of the primary
 nameserver to see why it thinks it is not authoritative. There's nothing in
 the log file of the primary server. When I reload the primary this is all
 that shows in the log:

 Jul 23 14:00:50 i2000 named[107]: reloading nameserver
 Jul 23 14:00:50 i2000 named[107]: couldn't create pid file
 '/var/run/named.pid'
 Jul 23 14:00:50 i2000 named[107]: Ready to answer queries.

 The relevant entry in my named.conf file for 176.171.63.in-addr.arpa looks
 like this:


 zone "176.171.63.in-addr.arpa" {
         type master;
         file "M/176.171.63.in-addr.arpa";

 };

 The relevant entry in the named.boot file (yes I know it's an old BIND)
 looks like this:

 secondary       63.171.176.in-addr.arpa         65.207.130.4
 176.171.63.in-addr.arpa

 The top part of the 176.171.63.in-addr.arpa file on the primary server
looks
 like this:

 $TTL 3h

 @ IN    SOA     ns.jellico.net. hostmaster.jellico.net. (
                 2002072305       ; Serial
                 3h      ; Refresh after 3 hours
                 1h      ; Retry after 1 hour
                 1w      ; Expire after 1 week
                 1h )    ; Negative caching TTL of 1 hour

 ; Name Servers

             IN NS     ns.jellico.net.



 Could someone help me solve this? Thanks so much.

 Lisa Casey






More information about the bind-users mailing list