dnswatcher

139 Commits 15 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	9b524e9d63	watcher: Port Change notifications list domains apart from hostnames (closes #248 ) check / check (push) Canceled after 0s Details A Port Change notification's `Hosts:` line listed a port's apex domains and hostnames together. It now has a `Domains:` line and a `Hostnames:` line, and leaves out one that would name nothing. A name is a domain when it is a configured domain, the rule record notifications already use to start `Domain:` or `Hostname:`; that rule is now one method, isDomain, which both use. The port entries saved in the state are unchanged. README describes the new lines. Model: opus-5-5	2026-10-02 10:42:07 +02:00
clawbot	e46db71821	dashboard, status API and notifications tell apex domains from hostnames (closes #224 ) check / check (push) Canceled after 0s Details An apex domain's own records are still saved with the hostnames' records, under the domain's name, so the port and TLS checks find its addresses. Notifications about them now start `Domain:`, decided by the configured domains. The dashboard and /api/v1/status, which read only the saved state, take a hostname entry whose name also has a domain entry as that domain's own records: the dashboard shows them in a second table under Domains, the API in the domain's `recordsByNameserver`, and neither lists or counts them as hostnames. The startup notification counts domains and hostnames from the configuration. README says which of a domain's own records are watched and how their changes are notified. Model: opus-5-5	2026-10-02 10:08:32 +02:00
clawbot	f99de191c0	watcher: change messages name only the record types that differ (closes #219 ) check / check (push) Canceled after 0s Details A Record Change notification printed the nameserver's whole old and new record sets in Go map syntax, and an Inconsistency notification the two nameservers' whole sets, so a one-address change had to be found by eye among kilobytes of unchanged TXT, CAA, MX and NS values. Both now list, in sorted order of type, only the record types whose values differ: a line naming the type, then each side's values separated by commas, or none when that side has no records of that type. The dashboard's Recent alerts shows the same text. Model: opus-5-5	2026-10-02 08:46:56 +02:00

Author

SHA1

Message

Date

clawbot

9b524e9d63

watcher: Port Change notifications list domains apart from hostnames (closes #248 )

check / check (push) Canceled after 0s

Details

A Port Change notification's `Hosts:` line listed a port's apex domains
and hostnames together. It now has a `Domains:` line and a `Hostnames:`
line, and leaves out one that would name nothing. A name is a domain
when it is a configured domain, the rule record notifications already
use to start `Domain:` or `Hostname:`; that rule is now one method,
isDomain, which both use. The port entries saved in the state are
unchanged. README describes the new lines.

Model: opus-5-5

2026-10-02 10:42:07 +02:00

clawbot

e46db71821

dashboard, status API and notifications tell apex domains from hostnames (closes #224 )

check / check (push) Canceled after 0s

Details

An apex domain's own records are still saved with the hostnames'
records, under the domain's name, so the port and TLS checks find its
addresses. Notifications about them now start `Domain:`, decided by the
configured domains. The dashboard and /api/v1/status, which read only
the saved state, take a hostname entry whose name also has a domain
entry as that domain's own records: the dashboard shows them in a second
table under Domains, the API in the domain's `recordsByNameserver`, and
neither lists or counts them as hostnames. The startup notification
counts domains and hostnames from the configuration. README says which
of a domain's own records are watched and how their changes are
notified.

Model: opus-5-5

2026-10-02 10:08:32 +02:00

clawbot

f99de191c0

watcher: change messages name only the record types that differ (closes #219 )

check / check (push) Canceled after 0s

Details

A Record Change notification printed the nameserver's whole old and new
record sets in Go map syntax, and an Inconsistency notification the two
nameservers' whole sets, so a one-address change had to be found by eye
among kilobytes of unchanged TXT, CAA, MX and NS values. Both now list,
in sorted order of type, only the record types whose values differ: a
line naming the type, then each side's values separated by commas, or
none when that side has no records of that type. The dashboard's Recent
alerts shows the same text.

Model: opus-5-5

2026-10-02 08:46:56 +02:00