nodo.ws reconnected as the garden’s custom domain

Date: 2026-09-01 Project: second-brain

What happened

nodo.ws stopped resolving (“se cayó”) — the zone had ZERO DNS records (it had never been wired; likely expected to point at the old deleted worker). Fixed by attaching the domain to the second-brain worker as a Workers Custom Domain via wrangler (routes: [{pattern, custom_domain: true}] in wrangler.jsonc → npm run deploy).

State

• nodo.ws + www.nodo.ws → second-brain worker (production), certs provisioned, DNS AAAA 100:: proxied (Cloudflare anycast).
• Edge verified 200 over both hostnames.
• Garden now live at https://nodo.ws (and second-brain.nef.workers.dev).

Gotchas

• The API to attach domains is PUT /workers/domains, but cloudflare_execute threw auth errors on zone-write ops — wrangler (user login) worked.
• Local machines on the home network still show 000 for a while: the ROUTER DNS cache holds the old NXDOMAIN (dig against [IP]/[IP] resolves, dig against [IP] doesn’t). Clears in 30-60 min or by switching the machine to [IP]/[IP]. Don’t redeploy chasing a 000 on a stale local resolver.
• Custom-domain DNS records appear as AAAA 100:: — that’s Cloudflare’s placeholder, expected, not a misconfiguration.