Skip to content

Clarify DNS64 routing, readiness, and prototype limits - #643

Draft
scotwells wants to merge 5 commits into
mainfrom
docs/dns64-prototype-routing
Draft

scotwells wants to merge 5 commits into
mainfrom
docs/dns64-prototype-routing

Conversation

@scotwells

Copy link
Copy Markdown
Contributor

Document how the DNS64 prototype uses internal service resources, node-local bidirectional routing, and routing metrics and logs. Clarify cleanup and rollback limits and the planned readiness agreement between the resolver VIP, Galactic route, and shared NAT64 prefix. Keep the product diagrams unchanged.

The document describes the current prototype and its limitations. It explicitly states that cross-node routing and health-based withdrawal are not implemented and production DNS64/NAT64 packet-path validation is incomplete. The prototype is not production-ready.

Validation: Markdown lint, reference/local-link checks, git diff --check, and go test ./internal/serviceroute pass. task ci stops during eBPF generation because llvm-strip is missing locally.

Related: Galactic routing #634, Galactic observability #635, Network API #27.

@privateip privateip mentioned this pull request Oct 4, 2026
@scotwells
scotwells force-pushed the feat/service-route-observability branch 12 times, most recently from dad6fb7 to f10c9fa Compare October 7, 2026 16:31
Base automatically changed from feat/service-route-observability to main October 7, 2026 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant