Each apex domain's own records are looked up and saved as a hostname's are, so that the port and TLS checks find its addresses (the fix for #19). Everything that reads the saved hostnames then treats the domain as a hostname too. With 7 domains and 9 hostnames configured, as the watcher starting log line said:
the dashboard's summary and counts.hostnames in /api/v1/status said 16 hostnames, and the startup notification counted the apex domains as hostnames as well;
the dashboard's Hostnames table lists every apex domain;
Record Change and Inconsistency notifications for the apex domain github.com begin "Hostname: github.com".
The README's apex domain section lists only NS changes and NS address changes as notified. It does not say that an apex domain's own records are watched and their changes notified as a hostname's are.
To see it, configure one apex domain and no hostname: the dashboard counts one hostname. checkDomain in internal/watcher/watcher.go saves the domain's records with SetHostnameState.
Definition of done
The dashboard, /api/v1/status and the startup notification count as hostnames only the hostnames configured.
A notification about an apex domain's records names it as a domain, not a hostname.
The dashboard shows an apex domain's records without listing the domain as a hostname.
README "DNS Domain Monitoring (Apex Domains)" says which of the domain's own records are watched and which changes to them are notified.
Model: opus-5-5
Found in the trial run for https://git.eeqj.de/sneak/dnswatcher/issues/149.
Each apex domain's own records are looked up and saved as a hostname's are, so that the port and TLS checks find its addresses (the fix for https://git.eeqj.de/sneak/dnswatcher/issues/19). Everything that reads the saved hostnames then treats the domain as a hostname too. With 7 domains and 9 hostnames configured, as the `watcher starting` log line said:
- the dashboard's summary and `counts.hostnames` in `/api/v1/status` said 16 hostnames, and the startup notification counted the apex domains as hostnames as well;
- the dashboard's Hostnames table lists every apex domain;
- Record Change and Inconsistency notifications for the apex domain `github.com` begin "Hostname: github.com".
The README's apex domain section lists only NS changes and NS address changes as notified. It does not say that an apex domain's own records are watched and their changes notified as a hostname's are.
To see it, configure one apex domain and no hostname: the dashboard counts one hostname. `checkDomain` in `internal/watcher/watcher.go` saves the domain's records with `SetHostnameState`.
## Definition of done
- The dashboard, `/api/v1/status` and the startup notification count as hostnames only the hostnames configured.
- A notification about an apex domain's records names it as a domain, not a hostname.
- The dashboard shows an apex domain's records without listing the domain as a hostname.
- README "DNS Domain Monitoring (Apex Domains)" says which of the domain's own records are watched and which changes to them are notified.
Model: opus-5-5
clawbot
added this to the 1.0 milestone 2026-10-02 07:35:33 +02:00
Built in #244: notifications about an apex domain's own records start Domain:, the dashboard shows those records in the Domains section and /api/v1/status in the domain's entry, and the dashboard, /api/v1/status and the startup notification no longer list or count the domain as a hostname. README's apex domain section says which of its records are watched and how changes are notified.
Model: opus-5-5
Built in https://git.eeqj.de/sneak/dnswatcher/pulls/244: notifications about an apex domain's own records start `Domain:`, the dashboard shows those records in the Domains section and `/api/v1/status` in the domain's entry, and the dashboard, `/api/v1/status` and the startup notification no longer list or count the domain as a hostname. README's apex domain section says which of its records are watched and how changes are notified.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found in the trial run for #149.
Each apex domain's own records are looked up and saved as a hostname's are, so that the port and TLS checks find its addresses (the fix for #19). Everything that reads the saved hostnames then treats the domain as a hostname too. With 7 domains and 9 hostnames configured, as the
watcher startinglog line said:counts.hostnamesin/api/v1/statussaid 16 hostnames, and the startup notification counted the apex domains as hostnames as well;github.combegin "Hostname: github.com".The README's apex domain section lists only NS changes and NS address changes as notified. It does not say that an apex domain's own records are watched and their changes notified as a hostname's are.
To see it, configure one apex domain and no hostname: the dashboard counts one hostname.
checkDomainininternal/watcher/watcher.gosaves the domain's records withSetHostnameState.Definition of done
/api/v1/statusand the startup notification count as hostnames only the hostnames configured.Model: opus-5-5
Built in #244: notifications about an apex domain's own records start
Domain:, the dashboard shows those records in the Domains section and/api/v1/statusin the domain's entry, and the dashboard,/api/v1/statusand the startup notification no longer list or count the domain as a hostname. README's apex domain section says which of its records are watched and how changes are notified.Model: opus-5-5