-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot establish connection to Quad9 via dnscrypt protocol #3947
Comments
Well, both AGH and dnslookup use the dnscrypt internally so the problem must be there. |
A quick test shows that Quad9 works over TCP only and this is what's causing the issue. |
I've opened a bug report, but fixing this on our side may take some time. Meanwhile, I've also contacted Quad9. Maybe this is a mistake on their side, having DNSCrypt work over TCP-only is rather strange. |
I am in contact with Quad9, it's confirmed that the problem is on their side. |
Ok. Thank You! Did they say, when this problem will be fixed? |
We have a fix being deployed out to the network right now. We had an incomplete roll out of the firewall rule that allowed DNSCrypt over UDP traffic. This should be corrected within the hour. Thanks for getting touch with our support team on this! |
Are this quad9 servers still working? dnscrypt-ip4-filter-priQuad9 (anycast) dnssec/no-log/filter 9.9.9.9sdns://AQMAAAAAAAAADDkuOS45Ljk6ODQ0MyBnyEe4yHWM0SAkVUO-dWdG3zTfHYTAC4xHA2jfgh2GPhkyLmRuc2NyeXB0LWNlcnQucXVhZDkubmV0 dnscrypt-ip4-filter-altQuad9 (anycast) dnssec/no-log/filter 149.112.112.9sdns://AQMAAAAAAAAAEjE0OS4xMTIuMTEyLjk6ODQ0MyBnyEe4yHWM0SAkVUO-dWdG3zTfHYTAC4xHA2jfgh2GPhkyLmRuc2NyeXB0LWNlcnQucXVhZDkubmV0 dnscrypt-ip4-filter-alt2Quad9 (anycast) dnssec/no-log/filter 149.112.112.112sdns://AQMAAAAAAAAAFDE0OS4xMTIuMTEyLjExMjo4NDQzIGfIR7jIdYzRICRVQ751Z0bfNN8dhMALjEcDaN-CHYY-GTIuZG5zY3J5cHQtY2VydC5xdWFkOS5uZXQ my log is full of these:
|
I have similar records in my logs, as the previous comment above from lordraiden, but not only on Quad9 servers. Adguard Home Version: v0.107.48
|
@renatoyamane please create a new issue. This has already been resolved. |
Are you still having this problem? I reported the issue below, but looks like I'm the only one with this problem: |
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Issue Details
Expected Behavior
A working connection via DNSCrypt protocol to Quad9 servers.
Actual Behavior
I went to:
https://raw.githubusercontent.com/Quad9DNS/dnscrypt-settings/main/dnscrypt/quad9-resolvers.md
I selected an Quad9 ipv4 DNS stamp (for DNSCrypt protocol).
Example:
sdns://AQYAAAAAAAAAEzE0OS4xMTIuMTEyLjEwOjg0NDMgZ8hHuMh1jNEgJFVDvnVnRt803x2EwAuMRwNo34Idhj4ZMi5kbnNjcnlwdC1jZXJ0LnF1YWQ5Lm5ldA
I pasted the DNS stamp into AdGuard Home, clicked on "Test upstreams" and got this error message:
Server "sdns://AQYAAAAAAAAAEzE0OS4xMTIuMTEyLjEwOjg0NDMgZ8hHuMh1jNEgJFVDvnVnRt803x2EwAuMRwNo34Idhj4ZMi5kbnNjcnlwdC1jZXJ0LnF1YWQ5Lm5ldA": could not be used, please check that you've written it correctly.
I have tried with other Quad9 ipv4 DNS Stamps (for DNSCrypt protocol). I always get the same error.
Unencrypted DNS, DoH and DoT to Quad9 DNS servers work just fine in AdGuard Home.
I downloaded ameshkov's dnslookup programm and I get the same results:
./dnslookup google.com sdns://AQMAAAAAAAAADDkuOS45Ljk6ODQ0MyBnyEe4yHWM0SAkVUO-dWdG3zTfHYTAC4xHA2jfgh2GPhkyLmRuc2NyeXB0LWNlcnQucXVhZDkubmV0
dnslookup v. v1.5.1
2021/12/14 13:32:39 Cannot make the DNS request: failed to fetch certificate info from sdns://AQMAAAAAAAAADDkuOS45Ljk6ODQ0MyBnyEe4yHWM0SAkVUO-dWdG3zTfHYTAC4xHA2jfgh2GPhkyLmRuc2NyeXB0LWNlcnQucXVhZDkubmV0, cause: read udp 192.168.6.6:46228->9.9.9.9:8443: read: no route to host
With dnscrypt-proxy v2.x I can establish the connection to Quad9 via dnscrypt protocol.
The text was updated successfully, but these errors were encountered: