Repository navigation
Conversation
Give networks a private DNS destination without managing DNS publication versions. Keep effective resolver settings available during observation outages and verify access against current network programming. Key changes: - Submit the context, region, and service destination to DNS - Keep DNS readiness separate from verified private network paths - Replace access when the DNS context lifetime changes
Preserve resolver context annotations and current subnet generation reporting.
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
1 participant
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.
Summary
Resources inherit private resolver addresses and the
datum.internalsearch domain from their attached network. Effective resolver settings remain read-only on interfaces. Network services submit context, region, and destination mappings to DNS and verify private paths through Galactic. The integration is disabled by default and retains applied settings during observation outages until explicit withdrawal.Test plan
Depends on Network #36, Galactic #851, and DNS #244.