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.
OK. > 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 mean. > 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 149.243.194.103.in-addr.arpa/PTR in 0.000744: failure/success [domain:243.194.103.in-addr.arpa,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. Cheers, b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
