Date: Thu, 13 Nov 1997 16:17:39 -0500 From: Mark Segal <mark@club-web.com> To: kbrown@primelink.com, isp@freebsd.org Subject: Re: Never before seen DNS error Message-ID: <346B6E73.847A0D7F@club-web.com> References: <346B499E.BD5490AE@primelink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?346B6E73.847A0D7F>