CodeGit/cloud-demo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: fix podinfo/hello-app CNAME target to match actual DNS pattern

Browse source 
An earlier commit (22acad8) pointed these at git.boglabob.com under the
assumption it was a canonical alias target for the server. Checking the
real zone file shows every other hostname (git, photos, music, etc.) is
a CNAME straight to the bare apex boglabob.com instead - git.boglabob.com
isn't special, just one more independent CNAME. Fix podinfo/hello-app to
match.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y4YNpuC2bgT224suQLLJ7B
This commit is contained in:
CodeGit 2026-09-04 10:20:17 +01:00
parent 854780c2bf
commit a803eda2c0
1 changed files with 10 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/03-flux.md
View file

@ -438,14 +438,18 @@ headlamp and the k3s API server are deliberately **not** exposed this way;
step 5 above and `docs/04-tofu.md` step 5 cover why and how to reach them
instead.
Two DNS records, as CNAMEs pointed at `git.boglabob.com` rather than
duplicating its IP directly — CNAME means "this name is an alias for that
one," so there's one place (that record) to update if the underlying IP
ever changes, instead of several:
Two DNS records, as CNAMEs pointed at the bare apex `boglabob.com` — the
zone's one actual A record — rather than duplicating its IP directly.
This matches every other hostname on this server (`git`, `photos`,
`music`, etc. are all `CNAME`s to the apex too); it's *not* about
`git.boglabob.com` being some special canonical host to alias through —
an earlier version of this doc got that wrong, pointing these two at
`git.boglabob.com` instead of the apex, inconsistent with every other
record in the zone:
```
podinfo.boglabob.com CNAME git.boglabob.com
hello.boglabob.com CNAME git.boglabob.com
podinfo.boglabob.com CNAME boglabob.com
hello.boglabob.com CNAME boglabob.com
```
Then in Caddy's own config, using the VM's pinned IP from stage 2: