Date: Tue, 22 Jul 1997 16:52:47 +1000 (EST) From: "Daniel O'Callaghan" <danny@panda.hilink.com.au> To: Swee-Chuan Khoo <sckhoo@asiapac.net> Cc: isp@FreeBSD.ORG Subject: Re: named-xfer problem Message-ID: <Pine.BSF.3.91.970722165117.869R-100000@panda.hilink.com.au> In-Reply-To: <Pine.SOL.3.96.970722141412.24645A-100000@topgun>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Jul 1997, Swee-Chuan Khoo wrote: > i am trying to troubleshoot the zone xfer problem > > here is the error mesg > > # /usr/local/sbin/named-xfer -z xxxxx.zone -f /tmp/xxxxx.zone > 202.135.xxx.168 > named-xfer[8636]: [202.135.xxx.168] not authoritative for xxxxx.zone, SOA > query got rcode 0, aa 0, ancount 0, aucount 13 > > but 202.135.xxx.168 machine is the authoritative server for > this zone. the other domain is ok and only this is having problem. 203.135.xxx.168 says it is *not* authoritative because there is an error in the zone file. Look in /var/log/messages on .168, or turn named on on .168. The secondary machine is OK. Danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.970722165117.869R-100000>