From owner-freebsd-isp Thu Nov 13 13:12:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA21491 for isp-outgoing; Thu, 13 Nov 1997 13:12:48 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from bert.club-web.com (bert.club-web.com [207.176.196.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA21480 for ; Thu, 13 Nov 1997 13:12:40 -0800 (PST) (envelope-from mark@club-web.com) Received: from club-web.com (ernie.club-web.com [207.176.196.12]) by bert.club-web.com (8.8.8/8.8.6) with ESMTP id QAA02739; Thu, 13 Nov 1997 16:15:46 -0500 (EST) Message-ID: <346B6E73.847A0D7F@club-web.com> Date: Thu, 13 Nov 1997 16:17:39 -0500 From: Mark Segal Organization: Club-Web Inc. X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: kbrown@primelink.com, isp@freebsd.org Subject: Re: Never before seen DNS error References: <346B499E.BD5490AE@primelink.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Kevin Brown wrote: > > Greetings! > > I have never seen the following DNS error appear before, and cannot find > anything which would lead me to find it's cause. If any of you might > have an idea, I would be most appreciative. > > ns2 named[PID]: sysquery: findns error (2) on ns1.primelink.com? > ns2 named[PID]: sysquery: findns error (2) on ns2.primelink.com? > > After several bouts with these errors, my primary zone expires, and no > resolution is provided to our domain. I am not having this problem with > any of the other 100 or so domains we host. To cure this, I simply > restart.named and it reloads the zone file, and it will work for several > more hours, then the errors start re-appearing, and the process > continues again. > > Thanks for your assistance, and direct response to this posting at: > kbrown@primelink.com > Could u post the db.primelink.com (ie the named file for the domain).. and the named.conf file.. The info might help.. i had a similar error when i accidently put secondary instead of primary for a zone.. i had both of them expire (ie the real primary and secondary).. mark -- Mark Segal mark@club-web.com System Administrator - Club-Web Inc.