Am 21.11.2019 um 11:47 schrieb Bind Mailinglist:
> Hello Ondřej
> Interesting case and not so easy to detect. But I was able to get a
> few steps further.
> As I have always to clear cache for host
> tm.inregion.waas.oci.oraclecloud.net I focused monitoring on that.
> 1.
> On my caching servers I
The cache shows you that the forwarder reported that there’s no such record
returned from the upstream resolvers.
The NXRRSET means - Non-eXistant Resource Record Set, e.g. your resolvers
cached the non-existence of the name returned from the upstream resolvers.
The other option would be runnin
Hello Ondřej
Many thanks for your answer. Hope debugging can help me without server
overloading.
They have around 1500 queries/s peakload during eveninghours. It will
need some time to log exactly this effect.
At the moment I have the following lines disabled:
// forwarders {
//
Hi,
you mentioned “forwarders” - what are these and how does answer look like
on the upstream forwarders?
I would recommend enabling higher debug level (start with -d 1) and look into
logs what was the answer from the forwarders preceding the failure.
Ondrej
--
Ondřej Surý — ISC
> On 20
Hello list
I'm glad there is such an active list. Hope there is anybody out there
who can help me with my little problem. :-)
We are running six bind server ( all Ubuntu LTS 18.04 with bind 9.11.3
), so they are pretty up to date.
Three of them have authoritative zones, one is for testing and two a
5 matches
Mail list logo
