A home or office network needs two things from its DNS. Devices should
find the services that run in the network by name, such as
pihole.home.example . Ads and trackers should not resolve at all. Pi-hole
does the second part. It answers with 0.0.0.0 for every domain on its
deny list and blocklists, and forwards the rest. The names of the local
services belong in a zone that a server holds with authority. PowerDNS
Authoritative Server holds that zone here, and external-dns writes a
record into it for every Kubernetes Service that asks for a name.
This post puts the three together from three
recipes that kadet-hub publishes for
Kapitan . The project is
pihole-powerdns
in kadet-hub/examples. Its check script deploys it to a new
kind cluster on every change and once a week, and fails
when a step below stops working.…