This does not occur when I trace route the specific TLS hostname that Adguard DNS gives me to put into my router via the 'router setup' on their website. I say that for two reasons:Ī) I can see the detailed ping results when running trace route. When I run a trace route on, the result also does not appear to be encrypted. Clearly I have very limited networking knowledge, but when I run a trace route on either 94.140.14.14 or 94.140.15.15, neither are encrypted IP's. Those default IP addresses (that you referenced above, and that I changed the router to reflect) do not appear to be encrypted. is there a way to get Adguard TLS set up properly with the settings available without having to do more 'invasive' things like installing Adguard via entware, etc? Perhaps I'll go that route at some point, but it seems a bit above my depth for the time being. From what I've read elsewhere, DoT doesn't use IP's like that, it just uses hostnames.Īlso, the drop downs for Adguard under 'preset servers' give you non-encrypted adguard ip addresses, 94.140.14.14 and 94.140.15.15, which means that they are not encrypted TLS addresses, which to me is strange why they would choose those for a DoT option. However, in the DNS over TLS drop down, the Merlin firmware forces you to give an IP address instead of just the TLS Hostname that Adguard gives me. Those plain addresses are of course unencrypted however, and I noticed that there is an option for DNS over TLS under the DNS Privacy Protocol setting in the Merlin firmware.

'You are using your private Adguard DNS Server' is the message that page gives me. So I recently set up Adguard DNS, added the 'plain DNS server addresses' (94.140.14.49 and 94.140.14.59) to my RT-AX88U with Merlin firmware as the DNS Server, and verified that it works by going here. Also tried following this guide, but can't complete it due to the following. I searched first but couldn't find a definitive answer.

Adguard dns review