4 Commits

Include renames

Author	SHA1	Message	Date
clawbot	67b67b8475	resolver, watcher: a domain's nameservers are only its own delegation (closes #222) ... When a domain's parent zone's servers answer NXDOMAIN, LookupNS returns ErrNXDomain. The watcher then saves the domain with no nameservers and nxdomain set, shown on the dashboard and in /api/v1/status, asks for none of its records and removes those saved, so its old nameservers go in one NS Change. A domain with no delegation of its own gets an empty set and its records are still asked at the zone it is in. FindAuthoritativeNameservers moves to a parent name only on one of those two answers; when the servers do not answer, it returns the error. After an upgrade, a domain without its own delegation that was saved with its parent zone's nameservers gets one NS Change; the README says so. Model: opus-5-5	2026-10-02 12:38:45 +02:00
clawbot	b43402a631	dashboard and status API list a port's domains apart from its hostnames (closes #245) ... A port entry in the state saves the apex domains that resolve to its address with its hostnames. The dashboard's Ports table now has a Domains column next to Hostnames, and a port entry in /api/v1/status has a `domains` list, with `hostnames` no longer holding a domain. A name is taken as a domain when it has a domain entry, as the dashboard and API already tell a domain's own records from a hostname's. Both read the split from one function, buildPorts. The state file is unchanged; README says its port `hostnames` include domains. Model: opus-5-5	2026-10-02 10:31:07 +02:00
clawbot	e46db71821	dashboard, status API and notifications tell apex domains from hostnames (closes #224) ... 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	250f3dd687	dashboard and status API show why a check failed (closes #225) ... /api/v1/status now gives `error` for each nameserver entry and certificate entry whose status is `error`, copied from the state, which already kept it. The dashboard shows that reason in place of the records for a failed nameserver, which used to show the same `-` as one that answered with no records, and across the CN, issuer and expiry cells for a failed certificate, wrapped at a width of 20rem so the long TLS error does not narrow the Endpoint column. The dashboard stylesheet is a trimmed build, so the new markup uses only classes the page already had. README Web Dashboard and HTTP API say so. Model: opus-5-5	2026-10-02 09:14:28 +02:00