Out-of-zone data mistaken for glue?

[Mark Andrews]

In message <4BE937B1.7070201 at imperial.ac.uk>, Phil Mayers writes:
> Following on from yesterdays query; if I have this zone:
> 
> test.com.		86400	IN	SOA	...
> test.com.		86400	IN	NS	...
> foo.test.com.		86400	IN	NS	ns.foo.test.com.
> ns.foo.test.com.	86400	IN	A	192.168.254.254
> www.foo.test.com.	86400	IN	A	192.168.1.1
> 
> ...this zone loads fine, and www.foo.test.com does *not* resolve, which 
> is as expected I guess. However, neither bind nor named-checkzone report 
> the non-glue A record as an error. Is this expected?
> 
(This is just curiosity - obviously it's a bad idea to populate zones 
> like this!)
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users

Named checks that NS's have A's or AAAA's it doesn't do the reverse
checks of A's and AAAA's having NS's.  The latter is more complicated
and is not required for correct operation.

Note also that UPDATE requires that you be able to add then remove
a delegating NS and get back the same zone so it is not a error to
have all sorts of stuff hidden beneath a zone cut.  You can also
build up the contents beneath a zone cut then remove the delegation.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org