You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the latest vesion of AdGuard Home on Linux server and AdGuard DNS free subscription there. Look like DoH and DoH3 especially works more unstable than other protocols:
Please test it too and confirm. Thank you.
Traceroute to AdGuard DNS
❯ traceroute 94.140.14.14
traceroute to 94.140.14.14 (94.140.14.14), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 0.129 ms 0.093 ms 0.073 ms
2 172.31.128.1 (172.31.128.1) 0.963 ms 1.329 ms 1.411 ms
3 172.17.77.11 (172.17.77.11) 1.033 ms 172.17.77.8 (172.17.77.8) 1.023 ms 1.084 ms
4 * 172.17.24.53 (172.17.24.53) 0.710 ms 0.786 ms
5 mow-b5-link.ip.twelve99.net (213.155.141.44) 0.698 ms 0.747 ms 0.768 ms
6 sto-bb2-link.ip.twelve99.net (62.115.141.22) 25.070 ms 23.173 ms 23.261 ms
7 * * *
8 datacamp-ic-382959.ip.twelve99-cust.net (213.248.93.223) 21.745 ms datacamp-ic-355851.ip.twelve99-cust.net (62.115.191.202) 21.884 ms 22.150 ms
9 vl202.sto-itx-dist-1.cdn77.com (79.127.192.35) 21.839 ms vl204.sto-itx-dist-2.cdn77.com (79.127.192.37) 20.672 ms vl202.sto-itx-dist-1.cdn77.com (79.127.192.35) 21.871 ms
10 dns.adguard-dns.com (94.140.14.14) 21.889 ms 21.915 ms 21.951 ms
Issue Details
Step to reproduce:
Install AdGuard Home;
Edit config and set AdGuard DNS upstream servers with DoH or DoH3 protocols;
Also you can try to set h3:// scheme and these directive too:
serve_http3: true
use_http3_upstreams: true
Expected Behavior
No response
Actual Behavior
Screenshots
Screenshot 1:
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Platform
Linux
Protocol
DNS-over-HTTPS
Do you use AdGuard app?
Yes I am
Your configuration
I have the latest vesion of AdGuard Home on Linux server and AdGuard DNS free subscription there. Look like DoH and DoH3 especially works more unstable than other protocols:
Please test it too and confirm. Thank you.
Traceroute to AdGuard DNS
❯ traceroute 94.140.14.14
traceroute to 94.140.14.14 (94.140.14.14), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 0.129 ms 0.093 ms 0.073 ms
2 172.31.128.1 (172.31.128.1) 0.963 ms 1.329 ms 1.411 ms
3 172.17.77.11 (172.17.77.11) 1.033 ms 172.17.77.8 (172.17.77.8) 1.023 ms 1.084 ms
4 * 172.17.24.53 (172.17.24.53) 0.710 ms 0.786 ms
5 mow-b5-link.ip.twelve99.net (213.155.141.44) 0.698 ms 0.747 ms 0.768 ms
6 sto-bb2-link.ip.twelve99.net (62.115.141.22) 25.070 ms 23.173 ms 23.261 ms
7 * * *
8 datacamp-ic-382959.ip.twelve99-cust.net (213.248.93.223) 21.745 ms datacamp-ic-355851.ip.twelve99-cust.net (62.115.191.202) 21.884 ms 22.150 ms
9 vl202.sto-itx-dist-1.cdn77.com (79.127.192.35) 21.839 ms vl204.sto-itx-dist-2.cdn77.com (79.127.192.37) 20.672 ms vl202.sto-itx-dist-1.cdn77.com (79.127.192.35) 21.871 ms
10 dns.adguard-dns.com (94.140.14.14) 21.889 ms 21.915 ms 21.951 ms
Issue Details
Step to reproduce:
Expected Behavior
No response
Actual Behavior
Screenshots
Screenshot 1:
Additional Information
No response
The text was updated successfully, but these errors were encountered: