Skip to content

Propose automatic private DNS names for Compute instances - #470

Draft
scotwells wants to merge 8 commits into
mainfrom
docs/internal-dns-compute
Draft

scotwells wants to merge 8 commits into
mainfrom
docs/internal-dns-compute

Conversation

@scotwells

@scotwells scotwells commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Proposes automatic private DNS names and resolver settings for Compute instances attached to a VPC. Every VPC uses the same default datum.internal domain with isolated records. Users can resolve short names within their VPC without choosing a DNS zone or maintaining address records.

The enhancement follows the template and covers VPC-scoped names, optional qualified peer aliases, search domains, public resolver status, internal authorization, commented YAML examples, address cleanup, publication permissions, feature flags, and local end-to-end release criteria. It distinguishes stable instance identity from future health-sensitive service discovery.

Validation

Checked YAML syntax, document links within the table of contents, code fences, and whitespace. This PR contains documentation only.

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