A Raspberry Pi that only does DNS
DNS for the house moved off the cluster onto a Raspberry Pi with Unbound. An update in the rack no longer takes the internet away from everyone downstairs.
DNS for the house used to run in a container on the old tower, and since May on pve-1. Every update of the cluster meant a minute in which no page would load, and a question from downstairs whether the internet was down. It runs on a Raspberry Pi now, which does nothing else.
Unbound
Unbound resolves names itself, starting at the root servers, and answers for the machines in the house under home.arpa, the name reserved for home networks.
server:
interface: 0.0.0.0
access-control: 10.0.0.0/8 allow
prefetch: yes
local-zone: "home.arpa." static
local-data: "opnsense.home.arpa. A 10.0.10.1"
local-data: "pve-1.home.arpa. A 10.0.10.11"
local-data: "pve-2.home.arpa. A 10.0.10.12"
local-data: "pve-3.home.arpa. A 10.0.10.13"
local-data: "nas.home.arpa. A 10.0.10.20"
local-data: "pi-dns.home.arpa. A 10.0.10.53"$ dig +short nas.home.arpa @10.0.10.53
10.0.10.20Why not on the cluster
Everything on the cluster depends on DNS, so DNS should not depend on the cluster. The Pi hangs on the wall beside the rack, draws 3 watts and has one job. The router hands out 10.0.10.53 as the DNS server for the whole house.
subscribe
New entries and the next chapter by mail, nothing else.