Hello,
If the issue is intermitting and can be mitigated by serving cached data,
maybe you can configure your recursive servers to serve expired data.
On Thu, Feb 29, 2024 at 8:20 AM Affan Basalamah via dnsdist <
dnsdist@mailman.powerdns.com> wrote:
> Thanks for your response,
>
> May I add
Thanks for your response,
May I add that it's not the authoritative DNS, but it's the ccTLD DNS
server (example like server for .com.country_names, .co.country_names, or
.net.country_names)
There was a time when this DNS server was down, all of the traffic from the
country's local ISP (who's
> On 28 Feb 2024, at 18:45, Frank Louwers wrote:
>
> My experience: Google tries damn hard (tm) to resolve any domain, regardless
> of the incorrect settings set by / behaviour of the auth.
>
> Reality is that quad8 can resolve way more than you typically can, once you
> start measuring.
My experience: Google tries damn hard (tm) to resolve any domain, regardless of
the incorrect settings set by / behaviour of the auth.
Reality is that quad8 can resolve way more than you typically can, once you
start measuring.
> On 28 Feb 2024, at 18:09, Nico Cartron via dnsdist
> wrote:
>
> On 28 Feb 2024, at 14:26, Affan Basalamah via dnsdist
> wrote:
>
>
> Hi,
>
> I'm responsible for managing DNS server for service providers, and they
> request that DNS server usually have some important domain from my country
> ccTLD that usually can't be resolved because of the their
Hi,
I'm responsible for managing DNS server for service providers, and they
request that DNS server usually have some important domain from my country
ccTLD that usually can't be resolved because of the their authoritative DNS
was not reliable, and every user usually contacted the service
