Adguard dns family12/13/2023 ![]() ![]() I guess the only thing left for me to figure out is how to make Adguard DNS recognize the connection from my router so that all the stats sync properly with Adguard DNS and therefore I could do manual blocking, etc. I can't figure out how to run the other tests suggested, Stubby, TCPDump, etc. But at least I know its working properly on my Windows machines. Either the Adguard test page is not able to properly determine its encryption status, or its just not working. All of my original tests were run from the Mac Mini. So there is something about running that test from my Mac Mini that does not translate properly. So I just went over to my Windows 11 PC (with adguard premium disabled) and ran the same tests on the Adguard DNS test, and it actually shows "DNS over TLS" as it should! When I trace route that TLS hostname, I can see it running the test, but it gives no data back on the different locations it's pinging, which indicates to me that the connection is encrypted.ī) When I do the Adguard DNS test with the settings as shown in the pic above, it tells me that I'm using my "private Adguard DNS Server", but the protocol is indicating that it's using the standard unencrypted protocol. ![]() 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.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |