🏗️ Building my home server P5: Network-wide ad blocking with Pi-hole

🏗️ Building my home server: Part 5 Network-wide ad blocking with Pi-hole In my previous blog post, I covered deploying containers, configuring UFW, and setting up Nginx as a reverse proxy for my services. In this post, I'm taking things a step further by adding network-wide ad blocking to my home lab using Pi-hole . Pi-hole is a DNS sinkhole that blocks ads and trackers at the network level, meaning every device on my local network benefits from it without needing any client-side software. It also comes with a slick web interface for monitoring DNS queries and managing blocklists. On top of that, I configured Pi-hole to handle local DNS resolution for all my home lab services, so I can access them by their subdomain names instead of remembering IP addresses and port numbers. 🤔 Why Pi-hole? Up until this point, I had been relying on the /etc/hosts file on each client device to resolve my *.arcade-lab.io subdomains to the server's local IP. This worked, but it was tedious to maintain acr