bind918 malfunction?

[Peter]

This one was accidentially not sent to the list, sorry!

On Thu, Sep 05, 2024 at 08:04:37PM +0200, Ondřej Surý wrote:
! I’m on my phone, so this is a long shot, but you can try disabling the qname minimization.

Thank You for the suggestion, I can try this occasionally. Rather
I'd prefer to figure out what exactly is going wrong. Looking
through the entire dialogue it appears as if the resolver just stopped in
midflight and gave back SERVFAIL, with no obvious reason.

After figuring out why assumedly my database started to quote
querystrings ;) I looked into the data of the day, I found something
interesting: there is again the resolver apparently giving up in
midflight, but this time there are some error messages:

Sep  5 17:18:33 <local1.info> conr named[4456]: resolver: info: loop detected resolving 'ns1.edns.t-ipnet.de/A'
Sep  5 17:18:33 <local1.info> conr named[4456]: resolver: info: loop detected resolving 'ns1.edns.t-ipnet.de/AAAA'
Sep  5 17:18:33 <local1.info> conr named[4456]: resolver: info: loop detected resolving 'ns2.edns.t-ipnet.de/A'
Sep  5 17:18:33 <local1.info> conr named[4456]: resolver: info: loop detected resolving 'ns2.edns.t-ipnet.de/AAAA'
Sep  5 17:18:33 <local1.info> conr named[4456]: resolver: info: loop detected resolving 'ns3.edns.t-ipnet.de/A'
Sep  5 17:18:33 <local1.info> conr named[4456]: resolver: info: loop detected resolving 'ns3.edns.t-ipnet.de/AAAA'
Sep  5 17:18:33 <local1.info> conr named[4456]: resolver: info: loop detected resolving 'ns4.edns.t-ipnet.de/A'
Sep  5 17:18:33 <local1.info> conr named[4456]: resolver: info: loop detected resolving 'ns4.edns.t-ipnet.de/AAAA'
Sep  5 17:18:33 <local1.info> conr named[4456]: resolver: info: loop detected resolving 'ns5.edns.t-ipnet.de/A'
Sep  5 17:18:33 <local1.info> conr named[4456]: resolver: info: loop detected resolving 'ns5.edns.t-ipnet.de/AAAA'
Sep  5 17:18:34 <local1.info> conr named[4456]: query-errors: info:
  client @0x885bd4160 192.168.97.23#3102 (_sip._udp.tel.t-online.de):
  view intra: query failed (failure) for _sip._udp.tel.t-on line.de/IN/SRV at query.c:7836
Sep  5 17:18:34 <local1.info> conr named[4456]: query-errors: info:
  client @0x87d9fc160 192.168.97.23#3102 (_sip._tcp.tel.t-online.de):
  view intra: query failed (failure) for _sip._tcp.tel.t-on line.de/IN/SRV at query.c:7836
Sep  5 17:18:34 <local1.info> conr named[4456]: query-errors: info:
  client @0x840265160 192.168.97.23#3102 (_sips._tcp.tel.t-online.de):
  view intra: query failed (failure) for _sips._tcp.tel.t-online.de/IN/SRV at query.c:7836

Looking further, there are more of these "loop detected", apparently for
random nameservers all around world. And also from 9.16, but they
didn't seem to harm back then.
Not sure what to make of this - it doesn't look good.


cheerio,
PMc