CoreDNS as my central DNS manager in my home(lab).
Currently two nodes are running CoreDNS with the same config for resilence. I really hate long DNS chains, because if something breaks in between, DNS is out ... wife and children scream ... me unhappy.
Current setup with five zones:
- .fritz.box - resolved to the provider-supplied router which also manages my network printer
- .home - forwarded to my UDM which runs DHCP in my home
- .lab.home - zone file which define s a wildcard to resolve all requests to my Traefik reverse proxy
- .consul - forwarded to Consul service catalog for service discovery
- . - everything else (internet) is either forwarded to AdGuard Home (and then to Cloudflare DNS) if the AdGuard service is running. If not, forward directly to the UDM. Nomad + Consul are amazing for this kind of templating and dynamic re-configuration.
CoreDNS as my central DNS manager in my home(lab).
Currently two nodes are running CoreDNS with the same config for resilence. I really hate long DNS chains, because if something breaks in between, DNS is out ... wife and children scream ... me unhappy.
Current setup with five zones:
- .fritz.box - resolved to the provider-supplied router which also manages my network printer
- .home - forwarded to my UDM which runs DHCP in my home
- .lab.home - zone file which define s a wildcard to resolve all requests to my Traefik reverse proxy
- .consul - forwarded to Consul service catalog for service discovery
- . - everything else (internet) is either forwarded to AdGuard Home (and then to Cloudflare DNS) if the AdGuard service is running. If not, forward directly to the UDM. Nomad + Consul are amazing for this kind of templating and dynamic re-configuration.
Works quite well for me :-)