intermittent SERVFAIL for high visible domains such as *.google.com
Brian J. Murrell
brian at interlinx.bc.ca
Mon Jan 22 13:09:27 UTC 2018
On Mon, 2018-01-22 at 12:45 +0000, Tony Finch wrote:
>
> They'll have a log category of edns-disabled.
But if the problem were EDNS, would it be so intermittent and always
fixable by rndc reload?
> But, looking through the
> code, if this is leading to lameness you will also get lame-servers
> log
> messages.
So just looking for lame servers will cover EDNS issues also then,
right?
> lame-servers is also a log category, and tends to be quite noisy
> about
> various problems :-)
Yeah. Must be disabled by default on EL7 I would guess, just because
it's so noisy.
> The tagged values there are various kinds of things that happened
> when
> resolving; the lame: tag is a count of the lame servers that were
> encountered, including both newly discovered lame servers and cached
> lame
> servers.
So, if lame servers were a problem with resolving ns[1-4].google.com,
then I would see messages like in my previous message with a lame:n tag
where n > 0, yes?
Cheers,
b.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20180122/52d8ed13/attachment.bin>
More information about the bind-users
mailing list