Bind 9.1.0 slave problem

Jim Reid jim at rfc1035.com
Wed Jan 31 18:48:45 UTC 2001


>>>>> "Owen" == Owen McShane <omcshane at vianetworks.co.uk> writes:

    Owen> Once I had managed to fix the numerous errors in the
    Owen> named.conf file, the server attempted to do it's transfers,
    Owen> but reported the following:

    Owen> /opt/named/sbin/named[22932]: dns_zone_load: zone somedomain.com/IN: could not find NS and/or SOA records
    Owen> /opt/named/sbin/named[22932]: dns_zone_load: zone somedomain.com/IN: has 0 SOA records
    Owen> /opt/named/sbin/named[22932]: dns_zone_load: zone somedomain.com/IN: no NS records

    Owen> Is this something to do with the master servers' zones not
    Owen> having the $TTL at the start of the zone? (They are running
    Owen> earlier versions of Bind)

No. It's because the zone file has no SOA or NS records. The error
messages could hardly be any clearer. Check the zone file on the slave
server if one exists there. If the file is broken, delete it and make
the slave server transfer it again. If the file's still broken, it
suggests there's a serious error on the master server that should be
reported in its logs.


More information about the bind-users mailing list