Repository navigation
Implement DNS64 for IPv6-only instance #689
Description
Summary
Make the multi-tenant DNS service synthesize AAAA records for IPv6-only instances resolving IPv4-only hostnames, so they can reach IPv4-only destinations through the NAT64 gateway's prefix.
Scope
- Synthesize AAAA from the A record when a query returns no native AAAA, using the tenant's NAT64 prefix.
- Read the prefix from the IGW as source of truth — no prefix duplication in DNS.
- Scope synthesis per-tenant private zone; optional per-zone disable for IPv6-strict workloads.
- Mark synthesized responses distinctly so debugging tools can flag them.
- Degrade safely (return no AAAA) if the prefix is unavailable.
Non-Goals
- No per-destination exclusion lists.
- No changes to the NAT64 data plane / session state.
Links
- Related: Internet NAT64 gateway #684 (NAT64 gateway)
- This supersedes DNS64 Support for Multi-Tenant DNS Service enhancements#792 (DNS64 enhancement).
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Activity
felixwidjaja commentedon Sep 16, 2026
Flagged as a possible overlap with datum-cloud/enhancements#866 (title-similarity 0.44, medium confidence). Not asserting either issue is a duplicate — flagging so a human can decide whether to merge, cross-link, or leave as companion issues.
privateip commentedon Oct 4, 2026
About the overlap flag: datum-cloud/enhancements#866 is the NAT64 data-path design, and this is DNS64. They're companions, not duplicates. #684 needs both, and this issue is already a sub-issue of #684.
[-]Implement DNS64 for IPv6-only instances (NAT64 gateway pairing)[/-][+]Implement DNS64 for IPv6-only instance[/+]