auto: docs sync 2026-08-24T12:00:05+00:00

Files changed: engine/.embcache.json engine/changelog.md engine/lint-report.md vault/.obsidian/workspace.json vault/docs/services/services.md vault/docs/software/caddy.md vault/docs/software/dns.md vault/runbooks/expose-service-edge2.md vault/runbooks/expose-service-home.md

vault/docs/software/dns.md

@@ -6,10 +6,10 @@ tags:
 aliases: []
 related:
   - [[caddy]]
-  - [[services]]
+  - [[expose-service-home]]
   - [[expose-service-contabo]]
-  - [[usenet]]
-  - [[expose-service-edge2]]
+  - [[services]]
+  - [[headscale-onboard-node]]
 updated: 2026-08-24
 ---
 # GoDaddy DNS Management
@@ -29,7 +29,7 @@ GoDaddy's API has two kinds of write endpoints for A records:
 - `PUT /v1/domains/<domain>/records/A` and `PUT /v1/domains/<domain>/records`
   — **replace every record of that type on the whole domain.**
 
-Both `k7zvx.com` and `echo6.co` front live production services (mail, auth,
+Both `k7zvx.com` and `echo6.co` front live production [[services]] (mail, auth,
 forge, vpn, vault, matrix, element, and more). Calling one of the record-SET
 endpoints to "add" a record would wipe every other A record on the zone.
 `godaddy-dns.py` only ever uses the single-record endpoint to write, and does