README: correct claims the code does not bear out (closes #108 )

Checked every README claim against the code on next and fixed the ones that were wrong or missing: what /metrics serves and when, what DNSWATCHER_MAINTENANCE_MODE does, CORS on the public routes, notification retries and the in-memory alert history, the certificate error field and old port entries in the state file, and the Design tree's missing files. Also corrected: CNAMEs are not followed for watched names, the root server list is never refreshed, the NS set is the zone's own answer, notification contents, and the system resolver being used for webhooks. Code problems found are filed separately. Model: opus-5-5
2026-10-01 23:45:33 +00:00
1 changed files with 0 additions and 1 deletions
@@ -412,7 +412,6 @@ This approach ensures:
 - Independence from any upstream resolver's cache or filtering.
 - Ability to detect split-horizon or inconsistent responses across authoritative
  servers.
- Visibility into the full delegation chain.

 CNAME chains are followed (with a depth limit to prevent loops) only to find the
 addresses of nameservers. A watched name's records are stored as its nameservers