Gandi

DNS hosting provider for the eblu.me domain, managed via Pulumi IaC.

Quick Reference

PropertyValue
Domaineblu.me
ProviderGandi LiveDNS
IaCpulumi/gandi/
Stackeblu-me
PATop://blumeops/gandi - blumeops/pat

What It Does

Gandi hosts the DNS records that make *.ops.eblu.me resolve to indri’s Tailscale IP. Since Tailscale IPs are not publicly routable, this gives services real DNS names while keeping them private to the tailnet. The target IP is resolved dynamically from indri.tail8d86e.ts.net at deploy time.

DNS Records

Private services (Caddy on indri)

RecordTypeValueTTL
*.ops.eblu.meAindri’s Tailscale IP300s
ops.eblu.meAindri’s Tailscale IP300s

Both records point to indri, which runs caddy as the reverse proxy for all private services.

Public services (Fly.io proxy)

RecordTypeValueTTL
docs.eblu.meCNAMEblumeops-proxy.fly.dev300s
cv.eblu.meCNAMEblumeops-proxy.fly.dev300s
forge.eblu.meCNAMEblumeops-proxy.fly.dev300s

Public CNAMEs point to flyio-proxy on Fly.io. See expose-service-publicly for adding new public services. See routing for the full service URL map.

TLS Integration

caddy uses this same Gandi PAT for ACME DNS-01 challenges to obtain a wildcard Let’s Encrypt certificate for *.ops.eblu.me. Caddy reads the PAT from ~/.config/caddy/gandi-token on indri, populated by ansible from 1Password.

Authentication

One Gandi Personal Access Token, shared by Pulumi and Caddy. Gandi caps PATs at 90 days; rotate every 60 days via rotate-gandi-pat.

ACME Challenge Cleanup

Caddy’s renewal flow leaves _acme-challenge.ops TXT orphans in the zone — a value-comparison bug in libdns/gandi v1.1.0 makes the cleanup phase a no-op. Run mise run dns-acme-cleanup periodically (alongside PAT rotation works well).