Re: [DNSOP] Unexpected REFUSED from BIND when using example config from RFC7706

On 7 Apr 2017, at 1:50, Bjørn Mork wrote:

> bert hubert <bert.hubert@powerdns.com> writes:
>> On Fri, Apr 07, 2017 at 10:20:00AM +0200, Bjørn Mork wrote:
>>> Just to avoid any confusion: Although I demonstrated the issue by
>>> running BIND on my laptop only, the real usage scenario is resolver
>>> service for a few million distinct administrative domains (aka
>>> "customers").  Changing the trust anchor is not an option.
>>
>> Perhaps https://lists.isc.org/mailman/listinfo/bind-users is a great 
>> place
>> to discuss BIND configurations and issues.
>
> Definitely.  Or even bind-workers when it comes to questions about the
> reason for making static-stub zones recursive only.
>
> The reason I ask here first, is because RFC 7706 includes a BIND
> specific configuration example (as well as examples for other 
> recursive
> server software).  So before considering changing config or code, I
> wanted to know the background of that example. Was there a real reason
> for the obscure(?)  "static-stub" zone type, or was that just an
> arbitrary choice?
>
> My apologies if this is considered OT here. I will shut up now.

The contents of an RFC that went through this WG is not off-topic. 
Please do not shut up. (The fact that some people took your original 
message into "how to fix it in BIND" instead of your original topic is 
not relevant.)

See the archives of this mailing list starting around November 11, 2014, 
in the thread titled "New Version Notification for 
draft-wkumari-dnsop-root-loopback-01.txt".

--Paul Hoffman