Recursive DNS
AI generated summary: I switched from AdGuard Home to a self-hosted PowerDNS Recursor for better control over my DNS infrastructure, reducing reliance on third-party resolvers.
I think I did not blog about it, but I switched back to a self-hosted AdGuard Home instance quite some time ago from NextDNS. To reduce my number of subscriptions, but also to increase my control over important infrastructure I use.
As upstreams in AdGuard Home, I used DNS4EU, Mullvad, and Quad9.
However, today, I switched to a self-hosted instance of [PowerDNS Recursor](https://w…
Recursive DNS
AI generated summary: I switched from AdGuard Home to a self-hosted PowerDNS Recursor for better control over my DNS infrastructure, reducing reliance on third-party resolvers.
I think I did not blog about it, but I switched back to a self-hosted AdGuard Home instance quite some time ago from NextDNS. To reduce my number of subscriptions, but also to increase my control over important infrastructure I use.
As upstreams in AdGuard Home, I used DNS4EU, Mullvad, and Quad9.
However, today, I switched to a self-hosted instance of PowerDNS Recursor. So no more reliance on third-party DNS resolvers, except the root and authoritative nameservers.
I try it with AdGuard Home first, as I later also want to set up a second PowerDNS Recursor instance on my mail server to make use of some more spam protection features.
Let’s see if any problems appear. When yes, “it was DNS”! 😅
Tags: AdGuard, DNS, NextDNS, Selfhosting