![]() Instead, running it in the existing Kubernetes cluster would allow to benefit from automated TLS certificate management already in place and leverage existing nodes. I therefore set out to migrate AdGuard Home to a public server, ideally running in my existing Kubernetes cluster because I did not want to rent an additional server dedicated to this. ![]() Last year, folks at AdGuard published a blog post on how to run and operate Adguard Home on a public server. So I wanted to benefit from this even on the go, regardless of the network I or any other family member is connected to. This has been running successfully for years now in my private home network setup. The Domain Name System (DNS) is a protocol allowing to translate human-readable domain names into IP addresses.Īfter experimenting with Adguard Home and other alternatives like Pi-Hole, I sticked to the former for its simplicity of use and overall resource usage. AdGuard Home provides a network-wide ads and tracking blocker, while also allowing to save some bandwidth usage (and indirectly CPU / memory consumption) while browsing.Īs a reminder, the Dynamic Host and Configuration Protocol (DHCP) allows to automatically assign IP addresses (from a range of addresses) and other configuration (like DNS servers) to devices joining a network. Since several years now, my network setup at home includes an instance of AdGuard Home running on a Raspberry Pi, and acting as both a DHCP and DNS server for all the family devices.
0 Comments
Leave a Reply. |