All projects

DNS Flood Fix

My own dashboard was rate-limiting my Pi-hole. The culprit: local records served with TTL 0, so nothing ever cached.

Homelab dashboard mockup with the Pi-hole tile highlighted in red and a note that every widget refresh triggers a DNS lookup

Context:

Pi-hole kept rate-limiting one client that wasn’t a real device. It turned out to be every tailnet device funnelled through one address, and the loudest of them was my own dashboard. Pi-hole v6 serves its local DNS records with TTL 0, so nothing downstream caches them and every widget refresh becomes a fresh lookup: up to 115 for one name in 15 seconds. One dnsmasq line, local-ttl=300, set through the container’s environment, took that to one lookup.

This is the short version. The full story covers the client that wasn’t a device, the wrong suspect I chased first, and three ways to apply the fix.