intermittent SERVFAIL for high visible domains such as *

Tony Finch dot at
Mon Jan 22 12:45:35 UTC 2018

Brian J. Murrell <brian at> wrote:
> What do EDNS problem messages look like?  Just something to grep for I
> mean.

They'll have a log category of edns-disabled. But, looking through the
code, if this is leading to lameness you will also get lame-servers log

> > or lame-servers complaints

lame-servers is also a log category, and tends to be quite noisy about
various problems :-)

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

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. The other error-related numbers are worth paying attention to, I
think - timeout, neterr, badresp, adberr, findfail, valfail.

f.anthony.n.finch  <dot at>  -  I xn--zr8h punycode
Tyne, Dogger: West, backing south, 5 or 6, occasionally 7 later. Slight or
moderate, occasionally rough. Occasional rain or showers. Good, occasionally

More information about the bind-users mailing list