From owner-freebsd-isp Thu Nov 13 10:42:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA06379 for isp-outgoing; Thu, 13 Nov 1997 10:42:53 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from ns1.primelink.com (mail.primelink.com [206.24.58.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA06373 for ; Thu, 13 Nov 1997 10:42:50 -0800 (PST) (envelope-from kbrown@primelink.com) Received: from mystic ([206.24.58.91]) by ns1.primelink.com (post.office MTA v1.9.3 ID# 0-11777) with ESMTP id AAA85 for ; Thu, 13 Nov 1997 12:48:29 -0600 Message-ID: <346B499E.BD5490AE@primelink.com> Date: Thu, 13 Nov 1997 12:40:31 -0600 From: Kevin Brown Reply-To: kbrown@primelink.com Organization: Huber & Associates X-Mailer: Mozilla 4.01 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-isp Subject: Never before seen DNS error X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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 -- ////////////////////////////////////////////////////////////////////// Kevin Brown kbrown@primelink.com