unapproved AXFR messages in syslog

Kevin Darcy kcd at daimlerchrysler.com
Mon Oct 23 21:21:12 UTC 2000


If the 80.141.209.in-addr.arpa has been delegated to your server, and you are not master, then you
*must* configure yourself as a slave for the zone.

Why is 64.142.14.2 trying to transfer that zone from your server? It should be getting it from the master
instead.

You shouldn't be using stub for these zones at all. Stub zones are not authoritative. All delegations
should refer to servers which are authoritative for the relevant domains. So stub zones are essentially
incompatible with delegated authority.


- Kevin

otrcomm***NO-SPAM***@wildapache**NO-SPAM***.net wrote:

> Hello,
>
> Could someone tell me what this message means in my syslog:
>
> Oct 22 22:12:30 pri named[23019]: unapproved AXFR from [63.142.14.2].3494 for
> "80.141.209.in-addr.arpa" (not master/slave)
>
> I read at http://www.acmebw.com/askmrdns/bind-messages.htm#idx_u
>
> that given a message like:
>
> unapproved AXFR from [132.174.12.141].48961 for "80.174.132.in-addr.arpa" (not master/slave)
>
> "...indicates that your name server denied a zone transfer of the zone 80.174.132.in-addr.arpa because
> it wasn?t authoritative for that zone and couldn?t serve a zone transfer.  This indicates a
> misconfiguration on the slave?s part (incorrectly listing your name server as the master for the
> zone)..."
>
> So I assume that my name server at 63.142.63.2 needs to be a slave to the nameserver at the
> 209.141.80.2 system.  Is this correct?
>
> If so, what is the syntax in the 209.141.80.2 system to accomplish this and, likewise, what is the
> corresponding syntax at the 63.142.14.2 system?
>
> What I currently have at the 209.141.80.2 system is the following in my named.conf file:
>
> zone "14.142.63.in-addr.arpa"{
>         type stub;
>         file "63.142.14";
>         masters {63.142.14.2 ; };
> };
>
> and the following in my named.conf file at the 63.142.14.2 system:
>
> zone "14.142.63.in-addr.arpa"{
>         type master;
>         file "63.142.14";
> };
>
> Obviously this is not correct, but this is what I was told to do by the DNS people at Winstar
> Broadband who assigned the 63.142.14.0/24 block to 209.141.80.2.
>
> Could some one please help me to get this straight?
>
> Thanks,
> Murrah Boswell






More information about the bind-users mailing list