Design DNS architecture

[morey-tech]

DNS management is all over the place for the homelab:

• pfSense is DNS forwarder for all of the networks.
  • Register DHCP leases in DNS forwarder
  • Register DHCP static mappings in DNS forwarder
  • Uses 1.1.1.1 and 8.8.8.8
• MaaS is a DNS server on the lab network for the maas.home.morey.tech.
• Cloudflare is a DNS server for the external DNS of morey.tech.
• rubrik is a DNS server for the rubrik.lab.home.morey.tech and example.morey.tech domain

[morey-tech]

After the homelab minification, the previous DNS infrastructure was dismantled. The current state is:

• pfSense is the default DNS server for DHCP clients and is used on the static lab network.
• The rubrik Kubernetes cluster serves DNS for the rubrik.lab.home.morey.tech and example.morey.tech domains.

Proposal 1: Use pfSense as the primary DNS server. Since the Netgate is a dedicated appliance, it would be an ideal host for the DNS infrastructure. Specific domains can be served by other scoped DNS servers.

Proposal 2: Use Pi 4 to host the primary DNS server for the network. It would be a dedicated low-power device, which could also run the Unifi controller. Plus the DNS server would be easier to automate compared to pfSense. router could still be used for DHCP domains.