ignoring out-of-zone data and MX records

[Mark.Andrews at nominum.com]

> On Fri, 16 Mar 2001 Mark.Andrews at nominum.com wrote:
> 
> > 
> > > I guess the question is:  How do you enter "out of zone" information,
> > > such as NS and MX records?  They simply do not show up in a query.
> > 
> > 	Well you problem below were the A records.  Also given that this
> > 	was only part of the zone.  Since you are flagging multiple errors
> > 	you are also most probably not driving named-checkzone correctly
> > 	and generating suprious errors as a result.
> > 
> > 	e.g.
> > 		named-checkzone newexample.com external.hosts
> > 
> > 	Mark
> > 
> > > 
> > > In article <98p8or$5s2 at pub3.rc.vix.com>, <Mark.Andrews at nominum.com> write
> s:
> > > >
> > > >	The line number is a indication only.
> > > >
> > > >	In this case host1.example.com and www.example.com are not
> > > >	part of newexample.com.
> 
> 
> I think I understand.  Unlike bind 8 configuration files, where it
> was normal (at least from my understanding) to include the A records
> for all of the nameservers, under bind 9 that is not acceptable.

	BIND 8 also complains.  It complains when it reads the
	out of zone name.  BIND 9 complains when the RRset is committed
	which is why the line numbers don't match.

> 
> I deleted the two A records for the nameservers from one test file
> and things look a lot better.

	Good.

	Mark
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com