[Unbound-users] stub-prime unexpected behavior
wouter at nlnetlabs.nl
Fri Apr 12 07:34:51 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
On 03/21/2013 05:21 PM, Aaron Hopkins wrote:
> On Thu, 21 Mar 2013, W.C.A. Wijngaards wrote:
>> Not for stub-prime, the newly introduced behaviour for 'normal
>> referrals' is to check at the parent as a last resort to get
>> information. When you add a stub-zone with stub-prime yes, then
>> this also activates.
>> Because it does not failover to the parent as a last resort.
> How does "stub-prime: yes, stub-first: no" differ from
> "stub-prime: yes, stub-first: yes", if the former falls back to
> using the roots? Doesn't "stub-first: no" tell it to not do that?
>> Not sure if I should fix this, or not. Is it merely unexpected,
>> or undesirable?
The issue is resolved in the svn. It now does not go to the
servers above configured stuff, if the configured servers fail. This
happens for stub-zone and forward-zone.
The actual bug was that it forgot the setting for stub-first when it
did the stub-prime.
> I would like "stub-prime: yes, stub-first: no" to still mean "I'm
> giving you a private zone that can't be reached from the roots,
> please don't try and ask them." If that's not what it means, I
> think updating the stub-prime documentation to include the
> fallback behavior is necessary.
> Thanks for looking at this,
> -- Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the Unbound-users