Maintained by: NLnet Labs

[Unbound-users] failing to stub an in-addr.arpa zone

W.C.A. Wijngaards
Tue Oct 21 17:06:05 CEST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

martin f krafft wrote:
> did not. I can imagine why.
> 
> I'd say that it shouldn't be required. If 168.192.in-addr.arpa is
> a default zone, then a stub-zone like 14.168.192.in-addr.arpa or
> even 168.192.in-addr.arpa should override that, no?

It is an entry in a different table internally.  The local zones, stubs,
forwarders, have their own lookup tables.  It seems to cause grief over
the forwarder/stub lookup as well.

Operators expect the most specific.  But the application has a simple
ordering, first check local-zone, then check forwards, then stubs.

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkj9790ACgkQkDLqNwOhpPgv8gCdFN0i0hki6DyyFMzkKg54QX/9
pdIAnjrKPLpm5979QB3kWZS/XcBwxmbN
=nSck
-----END PGP SIGNATURE-----