Files
computer-playbook/roles/sys-svc-dns/README.md
kevinveenbirkenbachandClaude Opus 5 c55f508e05 feat(readme): draw mandatory and disabled service relations
The cosmos generator linked a consumer to its provider only through an
'<role>' in group_names reference or an explicit provides: name. A hard
dependency has neither -- pinning the provider on unconditionally is
exactly what removes the Jinja reference the generator was reading -- so
web-svc-asset's bond to web-svc-file vanished from the diagram the moment
it became binding. Match a service key against the provider's own primary
key from the registry, in both directions.

Services the role turns off drew a solid 1:1 edge, claiming a mandatory
relationship for something that carries nothing at deploy time. They now
render as a red 0..0 edge; edge merging gained a real precedence so a
provider consumed through two keys stays live when only one is off.

Named colour, not hex: a '#' opens an entity code in the mermaid lexer and
turns the whole diagram into a parse error on GitHub.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-17 18:02:31 +02:00

2.5 KiB
Raw Permalink Blame History

sys-svc-dns

Description

Bootstrap and maintain DNS prerequisites for your web stack on Cloudflare.

This role validates credentials and (by default) ensures:

  • A (and optional AAAA) records on the apex (@) for all base SLD domains
  • Wildcard A/AAAA records (*.parent) for parent hosts via sys-dns-wildcards
  • (Optional) CAA records for Let’s Encrypt (kept as a commented block you can re-enable)

Runs once per play and is safe to include in stacks that roll out many domains.


Overview

This role cloudflare DNS bootstrap: parent host A/AAAA (and optional CAA), runs once per play.

Cosmos

The diagram places sys-svc-dns in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).

flowchart LR
    subgraph role [sys-svc-dns 💻]
        svc_svc_dns["svc-dns"]
    end

Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role's deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.

Features

  • Automated provisioning: Configured by Ansible without manual steps.

What it does

  1. Validate the Cloudflare API token (API.cloudflare.api_token) is present (early fail if missing).
  2. Ensure apex A/AAAA exist for every base SLD in SYS_SVC_DNS_BASE_DOMAINS:
    • Writes @ A → networks.internet.ip4
    • Writes @ AAAA → networks.internet.ip6 (only if global and present)
  3. (Optional) CAA records for all base SLDs (commented in the tasks; enable if you want CAA managed here).
  4. Ensure wildcard parent DNS exists (*.parent derived from children):
    • Delegates to sys-dns-wildcards
    • Creates A (and AAAA if enabled) wildcard records on the Cloudflare zone, optionally proxied.

Parent hosts example:
c.wiki.example.com → parent wiki.example.com (plus example.com apex)

Credits

Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).