Lame delegation error (was Re: problem with bind 8.2.3 )

Jim Reid jim at rfc1035.com
Mon Feb 19 19:33:10 UTC 2001


>>>>> "Philip" == Philip J Priest <phil at blkbox.com> writes:

    Philip> Im having some problems.  I made some changes to my boot
    Philip> files.  and I did increment the serial # of these files.
    Philip> this is my slave dns.  heres the error im getting in my
    Philip> syslog

    Philip> Feb 19 12:29:59 vbrg-ns named[28334]: Err/TO getting serial# for "66.52.200.IN-A DDR.ARPA" 
    Philip> Feb 19 12:29:59 vbrg-ns named[28334]: Err/TO getting serial# for "visualbridge.tv"
    Philip> Feb 19 12:29:59 vbrg-ns named-xfer[28337]: [209.247.124.3] not authoritative for 66.52.200.IN-ADDR.ARPA, SOA query got rcode 0, aa 0, ancount 0, aucount 13
    Philip> Feb 19 12:29:59 vbrg-ns named-xfer[28338]: [209.247.124.3] not authoritative for visualbridge.tv, SOA query got rcode 0, aa 0, ancount 1, aucount 0

Contact the DNS administrator of 209.247.124.3 and get her/him to fix
their name server. It's not authoritative for these two zones, which
is why your server can do zone transfers of them. This has probably
been caused by syntax errors in the master zone files that were not
noticed or fixed when the zones were last loaded. BTW, the above
address is not found in the masters{} clauses for these two zones in
the named.conf file you showed (12.19.102.16). Are you sure the config
file you posted is the one your name server is actually using? None of
the visualbridge.tv name servers are answering authoritatively for the
zone: they're all lame.

BTW, please try to pick a Subject: header that's not as vague as
"problem with bind 8.2.3". That could mean anything or nothing.


More information about the bind-users mailing list