[Unbound-users] failing to stub an in-addr.arpa zone
wouter at NLnetLabs.nl
Tue Oct 21 15:06:05 UTC 2008
-----BEGIN PGP SIGNED MESSAGE-----
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Unbound-users