Replies: 7 comments 1 reply
-
Please try using https://github.com/ameshkov/dnslookup and check what error does it show. |
Beta Was this translation helpful? Give feedback.
-
Appears to be no error. I saw someone in the Telegram chat today (I think) with the same issue. Perhaps an issue with DNS testing feature?
|
Beta Was this translation helpful? Give feedback.
-
Have you tried DOT and DOQ endpoints as well? |
Beta Was this translation helpful? Give feedback.
-
Yes. Weird behaviour. Added to the 'Additional information' at the bottom of OP Queries are being answered when saving the addresses but just the "Test Upstreams" feature is broken |
Beta Was this translation helpful? Give feedback.
-
If you would like a test profile I can PM you one on Telegram? |
Beta Was this translation helpful? Give feedback.
-
I guess that's not necessary, I can test it myself |
Beta Was this translation helpful? Give feedback.
-
After all, I cannot reproduce that issue. Here's what AGH does to check the upstream - it sends a DNS query to |
Beta Was this translation helpful? Give feedback.
-
Issue Details
Expected Behavior
When inserting DNS Server, in this case using DoH using NextDNS, then select 'Test Upstreams' AGH tests the server and gives information if successful or not.
Actual Behavior
Even though NextDNS and ADH logs requests and DoH is working, the test shows:
'Server "https://dns.nextdns.io/*retracted*/Home": could not be used, please check that you've written it correctly'
Screenshots
Additional Information
Issue does not occur using regular DNS or when using smaller links only occurs with encrypted DNS (DoH DoQ and DoT).
Not working: quic://Home-retracted.dns.nextdns.io
Working: quic://dns.nextdns.io
Not working: tls://Home-retracted.dns.nextdns.io
Working: tls://dns.nextdns.io
Not working: https://dns.nextdns.io/*retracted*/Home
Working: https://dns.nextdns.io/
Beta Was this translation helpful? Give feedback.
All reactions