[scotwells]

Summary

Proposes automatic private DNS names and resolver settings for Compute instances attached to a VPC. Every VPC uses the default datum.internal domain with isolated records. Users can resolve short names without choosing a DNS zone or maintaining address records. Compute publishes addresses and eligibility together through project-scoped permissions, while DNS reports publication status and network services manages resolver access.

Test plan

• Check document whitespace.
• Compare API examples with the DNS publication contract.
• Verify documentation CI.
• Verify required repository checks.

[ecv]

Requesting changes. Instance-name uniqueness is not designed. The decision list is on dns-operator#229.

Names collide in the flat namespace. Compute sets DNSRegistration.spec.name to the instance name, which is unique per namespace, not per VPC. Two namespaces on one Network, or an instance and a Connect export, can claim the same <name>.datum.internal. Specify the outcome: a suffix, a rejection, or a failed status. "A recreated instance can use the same hostname after the previous registration is withdrawn" is a race, and another publisher can take the name in the gap.

Also worth fixing:

• The doc copies DNSRegistration and DNSRecordContribution YAML that dns-operator owns, and the fields already differ. Link to it instead.
• Peered aliases such as web-01.application.production.datum.internal belong in the DNS or Network Services design. Drop them here, or mark them deferred.
• Published state is retained through a Compute outage with no maximum age. Record that as an accepted risk alongside the dns-operator decision.
• The doc says an instance on several VPCs uses one label in each, while a non-goal rules out several managed DNS contexts in one guest. Say what a guest with two VPC NICs gets.
• The four Go test files changed here (analysis_test.go, deploy_test.go, lookup_test.go, render_test.go) are unrelated to the doc. Explain them or drop them.

[scotwells]

Addressed in 6eb4407 (and the main merge 54d252b):

• Name uniqueness. The doc now describes DNS's rule: static records first, then the oldest registration. A losing registration reports NameConflict and shows up in Instance.status.dns with no hostname. There is no suffix and no retry. A recreated instance queues behind registrations already waiting for the name. Whether a replacement should keep its predecessor's name is listed as an open question. Today Compute only publishes for Networks in the Instance's own namespace, so the two-namespace collision can't happen yet. The doc says that cross-namespace attachments need a naming decision first.
• DNS types. The DNSRegistration/DNSRecordContribution YAML is gone. The doc links to the dns-operator types and only describes what Compute writes.
• Peered aliases. Deferred to the DNS and NSO designs.
• No maximum age. Recorded as an accepted risk, with a link to the dns-operator retention decision.
• Two VPC NICs. Records are published in both VPCs, but the guest itself gets no managed resolver and reports UnsupportedMultipleContexts, consistent with network-services-operator#589. The DNSConfigured reason is now Applied.
• Addresses. Addresses come from NetworkInterface allocations, with the Pod and node acting only as health gates, matching fix: Publish internal DNS from interface allocations #518.
• Test files. Main already has the same lint guards, so after merging main the PR only touches the doc.

[scotwells]

Following up on the peered-names note from the dns-operator#229 review: the doc has no peered-name user story anymore. In a448301 I renamed the remaining section to "Future work: peered networks" and added #229's statement that peering does not share zones or extend DNS access.

[ecv]

Approving at a448301. Name uniqueness is specified (oldest registration wins, NameConflict on the Instance, no suffix), the copied YAML is now a link, peered names are future work, a two-VPC guest gets UnsupportedMultipleContexts, and the unrelated test files are gone. Two text fixes before merge:

• Goals still says "Bound stale answers when instances disappear or publishers lose connectivity", which contradicts the accepted risk of no maximum age. Reword it to withdraw on confirmed deletion and retain during outages.
• The dns-operator link points at the fix/internal-dns-name-references branch. Repoint it to main or a SHA once dns-operator#244 lands.