Repository navigation
docs: name the Private DNS zone and instance hostnames - #119
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
State that every VPC's managed zone is datum.internal and that instances resolve at <instance>.instances.datum.internal, with examples, the search domain, TTL, and how instance names become DNS labels.
scotwells
force-pushed
the
docs/private-dns-names
branch
from
November 4, 2026 01:15
81f7fe5 to
d823c0b
Compare
Use a Workload-style Instance name in examples, drop the search-domain and name-conflict claims, describe label rules as code applies them, and point readers at status.dns for the exact hostname.
scotwells
marked this pull request as ready for review
November 4, 2026 01:22
kevwilliams
approved these changes
Nov 4, 2026
kevwilliams
left a comment
kevwilliams
left a comment
Contributor
There was a problem hiding this comment.
Verified datum.internal matches the default domain network-services-operator gives every network's resolver context.
This was referenced Nov 4, 2026
dlotterman
approved these changes
Nov 4, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Scot Schuchert-Wells
The Private DNS pages never said which names to use. This fills that in:
datum.internal. Each network has its own copy, so the same name returns different answers on different networks.<instance>.instances.datum.internal, using a real Workload-style name likeweb-default-us-central-1-0, with adig/curlexample, the 30 second TTL, how long names are shortened, and astatus.dnsexample.It also removes the old claim that Private DNS keeps the first of two colliding Instance names. In code both Instances' addresses are merged into one answer.
Values come from network-services-operator (default domain) and compute (the
instancesscope, label rules, and TTL) and dns-operator (record merging).Related: datum-cloud/enhancements#921