Gandi

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

Quick Reference

PropertyValue
Domaineblu.me
ProviderGandi LiveDNS
IaCpulumi/gandi/
Stackeblu-me

What It Does

Gandi hosts the DNS records that make *.ops.eblu.me resolve to indri’s Tailscale IP (100.98.163.89). 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, so if indri’s Tailscale IP changes, re-running the deployment is sufficient.

DNS Records

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 services. See routing for the full service URL map.

Pulumi Configuration

The Pulumi program lives in pulumi/gandi/:

  • __main__.py - Creates the two A records via pulumiverse_gandi
  • Pulumi.eblu-me.yaml - Stack config (domain, subdomain)

Stack config values:

KeyValue
blumeops-dns:domaineblu.me
blumeops-dns:subdomainops

A break-glass override is available via the BLUMEOPS_REVERSE_PROXY_IP environment variable, which bypasses dynamic IP resolution.

TLS Integration

caddy uses Gandi’s API separately (via GANDI_BEARER_TOKEN) for ACME DNS-01 challenges to obtain a wildcard Let’s Encrypt certificate for *.ops.eblu.me. This is a different credential from the Pulumi PAT.

Authentication

Gandi requires a Personal Access Token (PAT) for API access. PATs have a maximum lifetime of 90 days (currently set to 30). See gandi-operations for deployment and PAT cycling instructions.

  • gandi-operations - PAT cycling and deployment how-to
  • routing - Service URLs and routing architecture
  • caddy - Reverse proxy using Gandi for TLS
  • tailscale - Tailnet networking
  • indri - Server hosting Caddy (DNS target)