I set send-cookie no; globally to test this theory out but the pattern of
retries and timeout continued. Despite this I was able to determine the
retries/timeouts matches the same pattern as the resolver statistic for
truncated responses received which suggests they are related.
When I look
Well BIND 9.11+ supports DNS COOKIE by default and there are some servers that
mishandle EDNS requests with a DNS COOKIE option present. Unknown EDNS options
are supposed to be ignored, but there are servers/firewalls that just drop such
queries. Others return FORMERR, others return NXDOMAIN
Hi,
I have three centos 7 servers running bind acting as internal resolvers. There
was an update released that upgrades them from 0:9.9.4-74.el7_6.2 to
32:9.11.4-16.P2.el7_8.2. On performing this upgrade to one of the servers there
has been a notable increase in retry and timeout errors as
Dont flatter yourself troll, I've always been active on a number of
lists, but as I do have a life, I may not comment on every single thread
on every list.
Like I told you before stop being a f'wit and i'll have no reason to
warn anyone of how caustic you will get towards them, and we'll also
Hi,
We recently upgraded to 9.16.2 on FreeBSD 11.3 STABLE and after ~
week of use, it died this morning with the following assertion. Any
ideas what this might be about ?
May 3 05:36:27 ns named[845]: name.c:1738: INSIST(nlabels ==
name->labels) failed, back trace
May 3 05:36:27 ns
5 matches
Mail list logo
