fix(dns): durable coredns internal-zone forward#267
Merged
Conversation
OrbStack pods resolved internal hostnames via the laptop's upstream resolver, which can serve a stale/split-horizon view. Forward the internal zone to the internal DNS server authoritatively. - k8s/coredns/coredns-custom.yaml: kube-system configmap; CoreDNS imports *.server and reloads (Corefile has 'reload 15s'), so no restart needed. - deploy.sh: substitutes the zone + DNS server from Doppler (PROXMOX_SUBDOMAIN, NETWORK_CIDR_DNS) at deploy time — placeholders only, no literal domain/IP committed. - Replaces a runtime-only configmap so internal-hostname resolution survives make deploy. Assisted-by: Claude:claude-opus-4-8
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.
What
Adds a committed
coredns-customconfigmap (kube-system) that forwards the homelab internal DNS zone to the internal DNS server, and wiresdeploy.shto substitute the zone + server from Doppler at deploy time.Why
OrbStack pods resolve internal hostnames via the laptop's upstream resolver, which can serve a stale / split-horizon view. Forwarding the internal zone straight to the internal DNS server gives authoritative resolution. This replaces a runtime-only configmap so the fix survives
make deploy.How
k8s/coredns/coredns-custom.yaml: CoreDNS importskube-system/coredns-customkeys matching*.serverand auto-reloads (cluster Corefile hasreload 15s) — no CoreDNS restart.scripts/deploy.sh(Step 2.4): derives the zone fromPROXMOX_SUBDOMAINand the DNS server fromNETWORK_CIDR_DNS(Doppler),sed-substitutes the placeholders, applies to kube-system. Placeholders only — no literal domain/IP committed.Verified: substitution renders valid YAML;
kubectl apply --dry-run=clientpasses.