From owner-freebsd-isp  Mon Jul 21 23:53:18 1997
Return-Path: <owner-freebsd-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id XAA10865
          for isp-outgoing; Mon, 21 Jul 1997 23:53:18 -0700 (PDT)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA10858
          for <isp@FreeBSD.ORG>; Mon, 21 Jul 1997 23:53:11 -0700 (PDT)
Received: (from danny@localhost)
	by panda.hilink.com.au (8.8.5/8.8.5) id QAA20817;
	Tue, 22 Jul 1997 16:52:48 +1000 (EST)
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
In-Reply-To: <Pine.SOL.3.96.970722141412.24645A-100000@topgun>
Message-ID: <Pine.BSF.3.91.970722165117.869R-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


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