dnswatcher

115 Commits 15 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	d09822562d	resolver: pass over a server that answers SERVFAIL or refers no closer (closes #197 ) check / check (push) Failing after 2m8s Details When the resolver walks from the root servers towards a name, a server that answered SERVFAIL, or referred the query back to its own zone, up or sideways, ended the step, so finding a zone's servers gave up on the zone though its other servers would answer. Such a reply is now passed over for the zone's next server, as a timeout or a refusal already was. To tell a referral that leads closer to the name from one that does not, each walk keeps the zone of the servers it is asking. Other error replies, such as FORMERR, are passed over too. The walk that finds a nameserver's address shares the same server loop, so it changes too. Model: opus-5-5	2026-10-02 01:17:37 +02:00
clawbot	d2f154b2cf	resolver: error from ResolveIPAddresses when no nameserver answered (closes #190 ) check / check (push) Failing after 2m7s Details ResolveIPAddresses now returns an error, not no addresses, when no nameserver of the name's zone answered. A nameserver with status timeout or error is not an answer; one answer, even NXDOMAIN, is enough for an empty result without an error. When every server of a zone fails, FindAuthoritativeNameservers moves on to the parent name, whose servers only refer the query onward. Such a referral now has status error, so it is no answer either, and a hostname's saved records show it as error. The only caller, the nameserver address lookup, already keeps the previous addresses on an error; its comment no longer says the resolver hides this case. Model: opus-5-5	2026-10-02 00:28:53 +02:00
clawbot	95b017eb3e	resolver: lower-case DNS names in record values (closes #157 ) check / check (push) Successful in 58s Details Nameservers may answer with DNS names in any letter case. For eeqj.de, y.ns.joker.com answers in upper case while its peers answer in lower case, so the inconsistency check fired on every cycle. extractRecordValue now lower-cases CNAME, MX, SRV and NS targets, so the inconsistency check and the record-change check both compare names regardless of case. A, AAAA, TXT and CAA values are formatted as before. State saved before this change can hold upper-case names, which report a one-time record change on the first check after upgrading. Model: opus-5-5	2026-09-29 00:30:29 +02:00

Author

SHA1

Message

Date

clawbot

d09822562d

resolver: pass over a server that answers SERVFAIL or refers no closer (closes #197 )

check / check (push) Failing after 2m8s

Details

When the resolver walks from the root servers towards a name, a server
that answered SERVFAIL, or referred the query back to its own zone, up
or sideways, ended the step, so finding a zone's servers gave up on the
zone though its other servers would answer. Such a reply is now passed
over for the zone's next server, as a timeout or a refusal already was.
To tell a referral that leads closer to the name from one that does
not, each walk keeps the zone of the servers it is asking. Other error
replies, such as FORMERR, are passed over too. The walk that finds a
nameserver's address shares the same server loop, so it changes too.

Model: opus-5-5

2026-10-02 01:17:37 +02:00

clawbot

d2f154b2cf

resolver: error from ResolveIPAddresses when no nameserver answered (closes #190 )

check / check (push) Failing after 2m7s

Details

ResolveIPAddresses now returns an error, not no addresses, when no
nameserver of the name's zone answered. A nameserver with status
timeout or error is not an answer; one answer, even NXDOMAIN, is
enough for an empty result without an error.

When every server of a zone fails, FindAuthoritativeNameservers moves
on to the parent name, whose servers only refer the query onward. Such
a referral now has status error, so it is no answer either, and a
hostname's saved records show it as error. The only caller, the
nameserver address lookup, already keeps the previous addresses on an
error; its comment no longer says the resolver hides this case.

Model: opus-5-5

2026-10-02 00:28:53 +02:00

clawbot

95b017eb3e

resolver: lower-case DNS names in record values (closes #157 )

check / check (push) Successful in 58s

Details

Nameservers may answer with DNS names in any letter case. For eeqj.de,
y.ns.joker.com answers in upper case while its peers answer in lower
case, so the inconsistency check fired on every cycle. extractRecordValue
now lower-cases CNAME, MX, SRV and NS targets, so the inconsistency check
and the record-change check both compare names regardless of case. A,
AAAA, TXT and CAA values are formatted as before. State saved before this
change can hold upper-case names, which report a one-time record change
on the first check after upgrading.

Model: opus-5-5

2026-09-29 00:30:29 +02:00