Hello,
I run BIND 9.18.26 as a recursive, validating resolver. In my logs, I
noticed the following:
22-Apr-2024 19:25:59.614 lame-servers: info: chase DS servers
resolving '180.96.34.in-addr.arpa/DS/IN': 216.239.34.102#53
What does "chase DS servers" mean ?
Thanks,
- J
--
Visit https
They've got a number of problems. click-network.com is one of them.
https://dnsviz.net/d/click-network.com/dnssec/
There is some backstory. The City of Tacoma used to run broadband,
and that was Click! Network. The origin story is that this had something
to do with SCADA or power distribut
Hmm, I wonder if qname-minimisation is at issue here. My trace dies with:
85.191.131.in-addr.arpa. 1800 IN NS fs838.click-network.com.
85.191.131.in-addr.arpa. 1800 IN NS ns102.click-network.com.
couldn't get address for 'fs838.click-network.com': not found
couldn't get a
While BIND 9.18.21 with "qname-minimization strict;" SERVFAILs on the
following query, dig with +trace resolves it. Just a data point, and if
they fix their s**t and stop impersonating a signed zone then presumably
the example will resolve itself (pun intended).
dig -x 131.191.85.31
dig -x 131.19
4 matches
Mail list logo