DNS Problems
rloe...@hightowerinc.com
server is operating as the primary DNS for about 20 domains.
Everything is working fine except for one domain. I've added the zone
file. I've added the entry on named.boot. Nothing works. I've had a
number of people look at it and everyone says that all the periods are
in the right places and everything should work. When I try to nslookup
the domain all I get is the "Unknown/Invalid Domain" error. What could
I be missing? HELP!!!!!!!!!
Richard Loerzel
Senior Internet Specialist
HighTower Incorporated
www.hightowerinc.com
Sent via Deja.com http://www.deja.com/
Before you buy.
Jean-Pierre Radley
| My company has a SCO Openserver machine we are using for DNS. The
| server is operating as the primary DNS for about 20 domains.
| Everything is working fine except for one domain. I've added the zone
| file. I've added the entry on named.boot. Nothing works. I've had a
| number of people look at it and everyone says that all the periods are
| in the right places and everything should work. When I try to nslookup
| the domain all I get is the "Unknown/Invalid Domain" error. What could
| I be missing? HELP!!!!!!!!!
Have you tried running nslint?
--
Jean-Pierre Radley <j...@jpr.com> XC/XT Custodian Sysop, CompuServe SCOForum
Bill Vermillion
>My company has a SCO Openserver machine we are using for DNS. The
>server is operating as the primary DNS for about 20 domains.
>Everything is working fine except for one domain. I've added the zone
>file. I've added the entry on named.boot. Nothing works. I've had a
>number of people look at it and everyone says that all the periods are
>in the right places and everything should work. When I try to nslookup
>the domain all I get is the "Unknown/Invalid Domain" error. What could
>I be missing? HELP!!!!!!!!!
Well no one can guess what you are missing without posting all of
your files.
Small things like a missing period, substituting a # for a comment
instead of a ; - things like that.
But there are tools to help. nslint is one of them. I also had
a file pass nslint and lost one subnet. The clue there is to
look in the messages log file when named starts, as it will
typically put the error there, and often even give you a line
number to make the search easier.
Bill
--
Bill Vermillion bv @ wjv.com
Scott Taylor
Jean-Pierre Radley wrote:
>
> rloe...@hightowerinc.com opined (on Tue, Oct 19, 1999 at 09:57:11PM +0000):
> | My company has a SCO Openserver machine we are using for DNS. The
> | server is operating as the primary DNS for about 20 domains.
> | Everything is working fine except for one domain. I've added the zone
> | file. I've added the entry on named.boot. Nothing works. I've had a
> | number of people look at it and everyone says that all the periods are
> | in the right places and everything should work. When I try to nslookup
> | the domain all I get is the "Unknown/Invalid Domain" error. What could
> | I be missing? HELP!!!!!!!!!
>
> Have you tried running nslint?
>
What is nslint? Does it come with OSR5.0.5?
Jean-Pierre Radley
|
| What is nslint? Does it come with OSR5.0.5?
It finds lint in DNS files. No, it's not part of the any SCO OS.
ftp://ftp.ee.lbl.gov/nslint.tar.Z
Bill Vermillion
Jean-Pierre Radley <j...@jpr.com> wrote:
>Scott Taylor opined (on Thu, Oct 21, 1999 at 04:53:03AM +0000):
>| What is nslint? Does it come with OSR5.0.5?
>It finds lint in DNS files. No, it's not part of the any SCO OS.
> ftp://ftp.ee.lbl.gov/nslint.tar.Z
And just a 'heads-up' here. I had one instance where nslint, did
not find the errors. That's pretty darn good IMO.
However it showed up in a log file - edited here so the domain
name and servers remain incognito. Just another point to remember
when trying to find bugs.
----------------------
Oct 11 16:04:46 ns1 named[10911]: starting. named 8.1.2 Tue Nov 3 13:20:32 EST 1998 bi...@ns1.SOMEONE.com:/usr/ports/net/bind8/work/src/bin/named
Oct 11 16:04:46 ns1 named[10911]: sites/named.YYYYY:18: Database error ()
Oct 11 16:04:46 ns1 named[10911]: master zone "YYYYY.com" (IN) rejected due to errors (serial 1999101101)
Oct 11 16:04:46 ns1 named[10912]: Ready to answer queries.
----------------------
The errors pointed to line 18 in the specific domain file. I had
combed the files two or three times looking for errors before I
recalled that errors on startup up would be logged here. D'oh!