Spendlik/Claude_Homelab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update DNS/DDNS phases to reflect CNAME-based DNS architecture (2026-08-10 change) — removes obsolete per-subdomain A record + DDNS script step

Browse Source
This commit is contained in:
Spendlik 2026-08-11 08:40:18 +00:00
parent 2365cf69a0
commit f21561bab9
1 changed files with 10 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
114_koillection_deployment.md
View File

@ -3,7 +3,7 @@
> Status: **PLANNED** — not yet deployed > Status: **PLANNED** — not yet deployed
> CT ID: 114 · IP: 192.168.1.114 > CT ID: 114 · IP: 192.168.1.114
> Domain: `collections.spendlik.sk` > Domain: `collections.spendlik.sk`
> Last updated: 2026-07-03 > Last updated: 2026-08-11
--- ---
@ -290,22 +290,20 @@ docker compose restart koillection
## Phase 8 — DNS Record ## Phase 8 — DNS Record
> ℹ️ **Updated 2026-08-10**: All `*.spendlik.sk` subdomains are now **CNAME** records pointing at the root `spendlik.sk`. Only the root `spendlik.sk` A record holds an IP — WebSupport rejects any duplicate IP value elsewhere in the zone. Do **not** create an A record for this subdomain.
In WebSupport admin panel: In WebSupport admin panel:
1. Add A record: `collections` → current public IP 1. Add **CNAME** record: `collections` → `spendlik.sk`
2. **Check both DNS management pages** 2. Check both DNS management pages
3. Note the numeric record ID 3. Note the numeric record ID
4. Add to `00_index.md` DNS table 4. Add to `00_index.md` DNS table
--- > ✅ No DDNS updater step is needed for this subdomain. `ddns-update.sh` on CT 108 only updates the root A record on IP change; this CNAME resolves through automatically. (Previously this guide had a separate "add to DDNS script" phase — that step is obsolete under the current DNS architecture and has been removed.)
## Phase 9 — DDNS Updater (CT 108)
Enter CT 108, add `collections.spendlik.sk` to `/usr/local/bin/ddns-update.sh` using the record ID from Phase 8, following the existing script pattern.
--- ---
## Phase 10 — Authelia Protection (CT 102) ## Phase 9 — Authelia Protection (CT 102)
Enter CT 102, edit `/etc/authelia/configuration.yml`. Add to `access_control.rules`: Enter CT 102, edit `/etc/authelia/configuration.yml`. Add to `access_control.rules`:
@ -326,7 +324,7 @@ Add the Authelia middleware to the nginx vhost in CT 101 (follow the pattern fro
--- ---
## Phase 11 — First Login & Initial Setup ## Phase 10 — First Login & Initial Setup
Open `https://collections.spendlik.sk` from mobile data (hairpin NAT — never test from LAN). Open `https://collections.spendlik.sk` from mobile data (hairpin NAT — never test from LAN).
@ -338,7 +336,7 @@ On first load, Koillection will prompt you to create an admin account. Do so, th
--- ---
## Phase 12 — Collection Setup ## Phase 11 — Collection Setup
Recommended collection structure. Create each as a top-level Collection: Recommended collection structure. Create each as a top-level Collection:
@ -431,3 +429,4 @@ mkdir -p /opt/koillection/backups
| certbot corrupts nginx config | Always inspect after issuance | | certbot corrupts nginx config | Always inspect after issuance |
| Large photo uploads rejected | Increase `client_max_body_size` in nginx vhost | | Large photo uploads rejected | Increase `client_max_body_size` in nginx vhost |
| HTTPS redirect loop | Set `HTTPS_ENABLED=1` in `.env` and restart the koillection container after SSL is in place | | HTTPS redirect loop | Set `HTTPS_ENABLED=1` in `.env` and restart the koillection container after SSL is in place |
| DNS record type | Use CNAME → `spendlik.sk`, never a per-subdomain A record (see Phase 8) |