Am 08.02.22 um 13:34 schrieb Otto Moerbeek:
On Tue, Feb 08, 2022 at 01:24:03PM +0100, Thomas Mieslinger via Pdns-users
wrote:
In my experience pdns_recursor (okay, I tested only with older versions)
will not retry fast enough to have a 100% user experience.
It is worth the trouble to
On Tue, Feb 08, 2022 at 01:24:03PM +0100, Thomas Mieslinger via Pdns-users
wrote:
> In my experience pdns_recursor (okay, I tested only with older versions)
> will not retry fast enough to have a 100% user experience.
It is worth the trouble to test this again. Modern recursors are more
smart
On Tue, Feb 08, 2022 at 12:15:42PM +, Brian Candler via Pdns-users wrote:
> On 08/02/2022 12:08, Prochazka via Pdns-users wrote:
> >
> > Pdns recursor config:
> >
> > ...
> > forward-zones=
> > forward-zones+=some.domain.tld=AUTH1_ipv6
> > forward-zones+=some.domain.tld=AUTH1_ipv4
> >
On 08/02/2022 12:24, Thomas Mieslinger via Pdns-users wrote:
But remember, pdns_recursor does not do background checking whether a
Nameserver is alive. Background checking is only done by dnsdist afaik.
That's a good point. dnsdist continuously sends one query per second to
each backend to
In my experience pdns_recursor (okay, I tested only with older versions)
will not retry fast enough to have a 100% user experience.
I moved to bgp with my internal auth addresses. The auths check themself
and announce their service IP only if they are ready to answer.
If you don't have the
On 08/02/2022 12:08, Prochazka via Pdns-users wrote:
Pdns recursor config:
...
forward-zones=
forward-zones+=some.domain.tld=AUTH1_ipv6
forward-zones+=some.domain.tld=AUTH1_ipv4
forward-zones+=some.domain.tld=AUTH2_ipv6
forward-zones+=some.domain.tld=AUTH2_ipv4
Hello,
using pdns-recursor 4.5.7-1pdns.bullseye i am getting problem with dns
redundancy for records with expired ttl (best seen on low ttl). Forward
zones are used for internal domains only. Our clients has configured 3
recurcors (resolv.conf) and every recursor connect to any of the four
