Authority for subdomains

[The Tanster]

Barry Margolin <barmar at alum.mit.edu> wrote:

> In article <d2scfm$2nr3$1 at sf1.isc.org>,
>  The.Tanster at gmail.com (The Tanster) wrote:
> 
> > Barry Margolin <barmar at alum.mit.edu> wrote:
> > 
> > > In article <d2s32c$1gvc$1 at sf1.isc.org>,
> > >  The.Tanster at gmail.com (The Tanster) wrote:
> > > 
> > > > How can one set up a Master DNS server for a subdomain that one is
> > > > running on a private network to be authoritative for that subdomain only
> > > > (i.e. have a nslookup or dig query return an "authoritative" instead of
> > > > a "non-authoritative" answer when looking up a host only within that
> > > > subdomain)?  Can it be done in the named.conf through some keyword?
> > > > I've looked through the O'Reilly DNS & BIND book by Cricket Liu et al
> > > > and I can't find any information on this.  Thanks in advance.
> > > 
> > > zone "sub.domain.com" {
> > >   type master;
> > >   file "subdomain.db";
> > > };
> > > 
> > > and then put the subdomain data in subdomain.db.
> > 
> > Unfortunately, I've already done that but both nslookup and dig *STILL*
> > continue to give me a "non-authoritative" answer.
> 
> Then you've probably got a syntax error in the zone file.  Check your
> syslog for the error message, which includes the line number that it 
> failed on.  Or use named-checkzone.

I doubt it mainly because named is still running (it barfs and dies if
there's a syntax error on my system) and there's nothing in syslog or
any other logs that I can see.  I've seen the error messages and line
numbers in syslog whenever I make a typo in named.conf, etc, and named
spits up, so I know what you're referring to.

What is "named-checkzone"?  I don't have this utility on my system (I'm
running a DEC Tru64 version 5.0 system).