Sainthax
03-06-2002, 11:34 PM
I was checking my logs and I found this...
Mar 5 18:56:36 ns1 named[401]: sysquery: findns error (NXDOMAIN) on ns1.***********?
Mar 5 18:56:36 ns1 named[401]: sysquery: findns error (NXDOMAIN) on ns1.***********?
also these
Mar 5 19:07:19 ns1 named[401]: sysquery: findns error (NXDOMAIN) on raq.***********?
Mar 5 19:10:38 ns1 named[401]: sysquery: findns error (NXDOMAIN) on raq.***********?
the hostname of the server was raq but it was changed to ns1 awhile ago....everything seems to be working fine but I'm wondering if this is a problem waiting to happen?
dutchie
03-07-2002, 11:25 AM
Hi !
If you scroll a bit down you'll find this thread:
http://www.webhostingtalk.com/showthread.php?threadid=38346
Hope its any help.
Sainthax
03-09-2002, 02:22 AM
My error numbers are not the same...I went through all my records and I can't find the problem
still getting this, but I did notice that when I removed the PTR record it stoped....then when I put it back I got this message after restarting named
Mar 9 01:07:55 ns1 named[401]: sysquery: findns error (NXDOMAIN) on ns1.***********?
Mar 9 01:12:21 ns1 last message repeated 2 times
Sainthax
03-09-2002, 02:47 AM
ok after more playing I think I've really messed it up now
Mar 9 01:31:56 ns1 named[401]: reloading nameserver
Mar 9 01:31:56 ns1 named[401]: host name "-" (owner "ns1.***********::admin\@ns1.***********:10800:3600:604800:86400") IN (primary) is invalid - rejecting
Mar 9 01:31:56 ns1 named[401]: pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400:2: database naming error
Mar 9 01:31:56 ns1 named[401]: pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400:2: Database error near (bad name "-")
Mar 9 01:31:56 ns1 named[401]: pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400:3: Database error near ()
Mar 9 01:31:56 ns1 named[401]: pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400:4: Database error near ()
Mar 9 01:31:56 ns1 named[401]: pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400:5: Database error near ()
Mar 9 01:31:56 ns1 named[401]: pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400:6: Database error near ()
Mar 9 01:31:56 ns1 named[401]: pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400:7: Database error near ()
Mar 9 01:31:56 ns1 named[401]: pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400: Line 8: Unknown type: ).
Mar 9 01:31:56 ns1 named[401]: pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400:8: Database error near ())
Mar 9 01:31:56 ns1 named[401]: host name "-" (owner "ns1.***********::admin\@ns1.***********:10800:3600:604800:86400") IN (primary) is invalid - rejecting
Mar 9 01:31:56 ns1 named[401]: pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400:9: database naming error
Mar 9 01:31:56 ns1 named[401]: pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400:9: Database error near (bad name "-")
Mar 9 01:31:56 ns1 named[401]: Zone "ns1.***********::admin\@ns1.***********:10800:3600:604800:86400" (file pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400): no SOA RR found
Mar 9 01:31:56 ns1 named[401]: master zone "ns1.***********::admin\@ns1.***********:10800:3600:604800:86400" (IN) rejected due to errors (serial 0)
Mar 9 01:31:56 ns1 named[401]: Forwarding source address is [0.0.0.0].1075
Mar 9 01:31:56 ns1 named[401]: hint zone "" (IN) loaded (serial 0)
Mar 9 01:31:56 ns1 named[401]: Ready to answer queries.
also when I telnet in and ls the /named dir I see a new entry that reads...
pri.ns1.***********::admin@ns1.***********:10800:3600:604800:86400
Sainthax
03-10-2002, 04:30 AM
I figured it out myself :)
for referance:
I forgot to put in an A record pointing the the server's full name ns1.***********, and the PTR was causeing the error because there was no A record for that host name
I'm gonna go feel stupid now :dunce: