DNS module
Source: modules/dns/.
At a glance
Section titled “At a glance”| CLI | — |
| Subcommands | 0 |
| HTTP endpoints | see the route reference |
| Events emitted | — |
| Error codes | see the error code reference |
| Service classes | DNSService |
| Cross-module deps | — |
Source layout
Section titled “Source layout”modules/dns/├── errors.go├── service.go├── types.go└── providers/Errors
Section titled “Errors”Typed errors are catalogued in the error code reference with HTTP statuses and message templates.
Responsibilities
Section titled “Responsibilities”The dns module owns per-stack DNS record management — creating,
updating, and tearing down the DNS entries that expose a running stack
to the outside world. Providers are pluggable (see dns/providers/ or
equivalent): Cloudflare, Route53, a local stub, etc.
DNSService is called by the app lifecycle (install /
uninstall / ingress changes) and by cluster-level DNS sync (see
cluster/dns-provider-sync). It does
not own ingress rules themselves (those live in app/ingress.go), nor
HTTPS certificates (those come from the acme VApp on Traefik).
shc@docs:~$