10/8/2023 0 Comments Adguard dns not workingJust select wg0 in listen interface when you setup Adguardīut I couldnt get the wg0.To my understanding, my settings "translate" like so:įor DNS Client (WAN), I'm enabling DNSSEC, therefore for my custom DNS to work it must support DNSSEC (which it does if I'm not mistaken), then I choose dnsmasq as my validation method and I'm using a dnscrypt-proxy with manual configuration in order to use AdGuard personal DNS. Just select wg0 in listen interface when you setup said: I only selected eth0 Wireguard interface aloneĮth0 should be the NIC and wg0 as wireguard interface or whatever name was given for listening said:Įth0 should be the NIC and wg0 as wireguard interface or whatever name was given for listening interface I only selected eth0 Wireguard interface said: Once Wireguard interface is selected their are no unknown clients Saw the same issue when i did this exact mistake. Yes you might be 100% correct as probably in listening interface all interfaces were selected instead of only wireguard interface. Once Wireguard interface is selected their are no unknown said: This is a good one to start with: īut I do wonder is AdGuard listening on the correct interface? Since it shouldn't be listening on your public IP if you use WireGuard to connect. If your IP is dynamic, then you need to work with a blocklist. Whitelist only your IP address using either UFW/Iptables or in Adguard itself (Settings -> Allowed Clients).In you AdGuardHome.yml set refuse_any: true ANY queries have no valid reason to exist anymore and are mainly used by DNS amplification attacks ( ). Setup a rate limit in Adguard (Settings -> DNS Settings). But if you absolutely must DNS over UDP, you can try the following:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |