resolver: store a name's CNAME once per nameserver (closes #220) #236

Merged

clawbot merged 1 commits from issue-220-cname-stored-once into next

2026-10-02 09:09:52 +02:00

Author	SHA1	Message	Date
sneak	d60720816b	resolver: store a name's CNAME once per nameserver (closes #220 ) check / check (push) Waiting to run Details For a name with a CNAME, a nameserver answers a query of any type with that CNAME, and the records of every answer were added, so the CNAME was stored once for each of the eight record types asked for. collectAnswerRecords now adds each value once per record type. A state file saved before this holds the repeated values. Load keeps each record value once, so the first check after upgrading sees no record change and notifies nothing for them. Model: opus-5-5	2026-10-02 07:08:39 +00:00

Author

SHA1

Message

Date

sneak

d60720816b

resolver: store a name's CNAME once per nameserver (closes #220 )

check / check (push) Waiting to run

Details

For a name with a CNAME, a nameserver answers a query of any type with
that CNAME, and the records of every answer were added, so the CNAME
was stored once for each of the eight record types asked for.
collectAnswerRecords now adds each value once per record type.

A state file saved before this holds the repeated values. Load keeps
each record value once, so the first check after upgrading sees no
record change and notifies nothing for them.

Model: opus-5-5

2026-10-02 07:08:39 +00:00