Skip to content

docs: propose internal DNS architecture and API design - #229

Draft
scotwells wants to merge 27 commits into
mainfrom
docs/internal-dns-architecture
Draft

scotwells wants to merge 27 commits into
mainfrom
docs/internal-dns-architecture

Conversation

@scotwells

@scotwells scotwells commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Propose private DNS names that resources can resolve within their VPC. Describe shared regional capacity, tenant isolation, and automatic names in the default internal domain. Product services publish addresses and eligibility together, while network services supplies private access intent and DNS manages serving readiness. Include annotated API examples and diagrams that explain integration boundaries and continued resolution during control plane outages.

Test plan

  • Follow the enhancement template.
  • Review annotated API examples against the proposed implementation.
  • Review ownership, tenant isolation, and outage behavior.
  • Confirm CI succeeds.

@scotwells scotwells changed the title docs: propose internal DNS component architecture docs: propose internal DNS architecture and API design Oct 8, 2026
@scotwells
scotwells marked this pull request as ready for review October 8, 2026 21:25
@scotwells
scotwells requested a review from a team as a code owner October 8, 2026 21:25
privateip
privateip previously approved these changes Oct 8, 2026
@scotwells
scotwells requested a review from privateip October 12, 2026 16:55
Describe atomic product publication, fixed query protocols, and DNS-owned
access ordering. Resolver contexts directly own their managed zones and
associations while preserving tenant isolation and outage continuity.
Keep consumer access examples focused on destination intent and describe
mapping versions only in DNS service contracts.
@scotwells
scotwells marked this pull request as draft October 13, 2026 18:34
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.

2 participants