A later improvement, filed on sneak's ruling on #233 (comment 115468, 2026-10-03 12:10 UTC): when a name's answers change, notifying is correct, and that stays the default. This issue adds a way for an admin to turn off that one notification for a specific host.
Example: github.com's nameservers rotate their answers (140.82.121.3 at one check, 140.82.121.4 at the next), so every check sends a record-change notification. An admin watching github.com can switch that notification off for github.com only, and every other notification for it, and everything for every other host, stays on.
Definition of done
A per-host setting turns off the record-change notification for that host only; the default is on.
Turned off for a host, a change in that host's answers is still recorded as it is today; only the notification is suppressed.
The README describes the setting next to the description of record-change notifications.
Tests against real DNS (never mocked) cover a host with the setting on and off.
Lands on next after an independent review. This is a later improvement: it does not block 1.0.
Model: opus-5-5
A later improvement, filed on sneak's ruling on https://git.eeqj.de/sneak/dnswatcher/issues/233 (comment 115468, 2026-10-03 12:10 UTC): when a name's answers change, notifying is correct, and that stays the default. This issue adds a way for an admin to turn off that one notification for a specific host.
Example: `github.com`'s nameservers rotate their answers (`140.82.121.3` at one check, `140.82.121.4` at the next), so every check sends a record-change notification. An admin watching `github.com` can switch that notification off for `github.com` only, and every other notification for it, and everything for every other host, stays on.
## Definition of done
- A per-host setting turns off the record-change notification for that host only; the default is on.
- Turned off for a host, a change in that host's answers is still recorded as it is today; only the notification is suppressed.
- The README describes the setting next to the description of record-change notifications.
- Tests against real DNS (never mocked) cover a host with the setting on and off.
- Lands on `next` after an independent review. This is a later improvement: it does not block 1.0.
Model: opus-5-5
clawbot
self-assigned this 2026-10-03 14:26:15 +02:00
Duplicate of #255, which the dnswatcher manager filed four minutes earlier for the same ruling. Closing.
Model: opus-5-5
Duplicate of https://git.eeqj.de/sneak/dnswatcher/issues/255, which the dnswatcher manager filed four minutes earlier for the same ruling. Closing.
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.
A later improvement, filed on sneak's ruling on #233 (comment 115468, 2026-10-03 12:10 UTC): when a name's answers change, notifying is correct, and that stays the default. This issue adds a way for an admin to turn off that one notification for a specific host.
Example:
github.com's nameservers rotate their answers (140.82.121.3at one check,140.82.121.4at the next), so every check sends a record-change notification. An admin watchinggithub.comcan switch that notification off forgithub.comonly, and every other notification for it, and everything for every other host, stays on.Definition of done
nextafter an independent review. This is a later improvement: it does not block 1.0.Model: opus-5-5
Duplicate of #255, which the dnswatcher manager filed four minutes earlier for the same ruling. Closing.
Model: opus-5-5