Mark Andrews wrote:
> > On 8 Apr 2021, at 00:37, Tony Finch wrote:
> >
> > Forward zones require the upstream server to be recursive too.
>
> More correctly, the upstream server has to serve the entire namespace being
> forwarded if it does not off recursion to the client for forwarding to
>
Chuck, Tony,
Thank you all for sharing the ideas.. very much appreciated.
Thank you
Kind Regards,
Ravi Kota
On Wed, Apr 7, 2021 at 7:25 PM wrote:
> Send bind-users mailing list submissions to
> bind-users@lists.isc.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
t;
> 1) A non-recursive one in the backend containing your authoritative
> zones only. This can be a hidden master setup, somewhat like what you
> are using now.
>
> 2) The one your users access has recursion enabled, and contains stubs
> to the authori
> On 8 Apr 2021, at 00:37, Tony Finch wrote:
>
> Chuck Aurora wrote:
>>
>> A stub or static-stub zone would not require recursion. In that case
>> named is asking for authoritative data from upstream. But type
>> forward zones indeed cannot work if recursion is disabled.
>
> Be careful
John,
please report the issue to the ISC GitLab.
Thanks,
--
Ondřej Surý — ISC (He/Him)
My working hours and your working hours may be different. Please do not feel
obligated to reply outside your normal working hours.
> On 7. 4. 2021, at 19:32, John Thurston wrote:
>
> I now see this same
I now see this same behavior running BIND 9.16.12 on Ubuntu
I have never seen it on my instances running 9.11.x on Centos
I'd sure like to figure out why (or even when) it stops listening on
port 953. Does anyone have any suggestions?
--
Do things because you should, not just because you
Chuck Aurora wrote:
>
> A stub or static-stub zone would not require recursion. In that case
> named is asking for authoritative data from upstream. But type
> forward zones indeed cannot work if recursion is disabled.
Be careful in this kind of situation to be very clear about which client
or
On 2021-04-07 03:59, Marki wrote:
To elaborate a little bit on that... Indeed that is how it works,
unfortunately. When you start using forwarders or stubs, recursion
needs to be enabled because you're no longer looking for your own
authoritative data only.
A stub or static-stub zone would not
Hello,
On 4/7/2021 10:35 AM, Matus UHLAR - fantomas wrote:
On 06.04.21 22:47, RK K wrote:
In this scenario, in-order for the secondary server to forward the DNS
query to an external DNS server, is it required to enable the
recursion in
the global options on the secondary servers?
yes.
On 06.04.21 22:47, RK K wrote:
We have a set of BIND primary servers (MASTERs) and a set of secondary
servers (slaves to the MASTERs).
The secondary BIND DNS servers disabled recursion ( with "*recursion no;" *)
in the global options.
All the applications/systems do use secondary DNS servers for
10 matches
Mail list logo
