intermittent SERVFAIL for high visible domains such as *

Brian J. Murrell brian at
Mon Jan 22 12:21:18 UTC 2018

On Mon, 2018-01-22 at 12:04 +0000, Tony Finch wrote:
> That indicates that it has already marked the servers as lame, so the
> packet trace isn't going to tell you what caused the lameness.


> The thing to look out for is the minutes before the outage starts -
> see
> what kind of failures you get.
> Also, check the logs for EDNS

What do EDNS problem messages look like?  Just something to grep for I

> or lame-servers complaints

Does the "lame:1" in this message indicate lameness:

18-Jan-2018 11:12:47.103 fetch completed at resolver.c:3074 for in 0.000744: failure/success [,referral:0,restart:1,qrysent:0,timeout:0,lame:1,neterr:0,badresp:0,adberr:0,findfail:0,valfail:0]

Of course, that one is irrelevant to my situation, I'm just using it as
an example of how to find lame delegations.

-------------- 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: <>

More information about the bind-users mailing list