Authority zones

[Wouter Wijngaards]

Hi Fredrik,

Because the zone is listed to be served.  It is then available straight
away, with actual authority queries and answers.

The other configuration, where the zone is used to speed up processing
(root copy set up), is not, I thought, as straightforward.  So I made
the one I thought was more straightforward the default.  I.e. loading a
zone for authority service without other config, is that.  And enabling
the hyper-local root zone, needs some option to perform the local loop
portion.

So, I thought it would be less 'surprising', than local-loop processing
only, or not using it for local-loop processing either.

Best regards, Wouter

On 5/21/19 11:07 PM, Fredrik Pettai via Unbound-users wrote:
> Hi,
> 
> I'm playing around with the Authority zone support in unbound.
> 
> A thing that puzzled me is why "for-downstream: yes" is the default?
> 
> (I mean, a resolvers main task is to resolve names rather than serving
> me "hints")
> 
> What was the thought behind the current default?
> 
> 
> Thx,
> 
> /P
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20190528/20837606/attachment.bin>