CNAME chain + per-NS storage interaction: incomplete IP resolution #61

Closed
opened 2026-03-01 23:24:22 +01:00 by clawbot · 1 comment
Collaborator

If hostname A CNAMEs to hostname B, and different NSes return different CNAME targets, the per-NS record storage correctly captures this. But the IP resolution for port checks needs to follow ALL CNAME chains across ALL NSes to build the complete IP set.

The spec does not clarify this.

Ref: issue #5 item 9

If hostname A CNAMEs to hostname B, and different NSes return different CNAME targets, the per-NS record storage correctly captures this. But the IP resolution for port checks needs to follow ALL CNAME chains across ALL NSes to build the complete IP set. The spec does not clarify this. Ref: [issue #5](https://git.eeqj.de/sneak/dnswatcher/issues/5) item 9
clawbot added the bot label 2026-03-01 23:24:22 +01:00
Owner

hmm, let's assume that we're monitoring zones not run by idiots

hmm, let's assume that we're monitoring zones not run by idiots
sneak closed this issue 2026-03-01 23:28:09 +01:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/dnswatcher#61