The problem encountered when setting the upstream DNS to ControlD’s server

[bestpika]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to report a bug and not ask a question or ask for help

• I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Windows, AMD64 (aka x86_64)

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.108.0-a.658+2bfc9fcb

Action

Set the upstream DNS to ControlD’s server.

https://freedns.controld.com/p1
h3://freedns.controld.com/p1
quic://p1.freedns.controld.com
tls://p1.freedns.controld.com

Expected result

N/A

Actual result

When testing the upstream servers, only DoH and DoT are functioning properly, while DoH3 and DoQ are showing error messages. However, among DoH and DoT, only DoT can be used, but it shows many NOTIMP error messages.
In addition, DoH, DoH3, and DoQ are all not working.
However, when I tested using https://github.com/natesales/q, all servers responded normally.
I asked ControlD about this, but they insisted that they have no issues.

By the way, I have two computers in different locations with different ISPs that have the same problem.

Additional information and/or screenshots

DoH

q cdn.kingstone.com.tw -v -s https://freedns.controld.com/p1
time="2023-08-23T23:01:34+08:00" level=debug msg="RR types: [A AAAA NS MX TXT CNAME]"
time="2023-08-23T23:01:34+08:00" level=debug msg="Using HTTP(s) transport"
time="2023-08-23T23:01:34+08:00" level=debug msg="[http] sending GET request to https://freedns.controld.com:443/p1?dns=aacBAAABAAAAAAAAA2NkbglraW5nc3RvbmUDY29tAnR3AAABAAE"
time="2023-08-23T23:01:34+08:00" level=debug msg="[http] sending GET request to https://freedns.controld.com:443/p1?dns=FTMBAAABAAAAAAAAA2NkbglraW5nc3RvbmUDY29tAnR3AAAcAAE"
time="2023-08-23T23:01:34+08:00" level=debug msg="[http] sending GET request to https://freedns.controld.com:443/p1?dns=tssBAAABAAAAAAAAA2NkbglraW5nc3RvbmUDY29tAnR3AAACAAE"
time="2023-08-23T23:01:34+08:00" level=debug msg="[http] sending GET request to https://freedns.controld.com:443/p1?dns=mFUBAAABAAAAAAAAA2NkbglraW5nc3RvbmUDY29tAnR3AAAPAAE"
time="2023-08-23T23:01:34+08:00" level=debug msg="[http] sending GET request to https://freedns.controld.com:443/p1?dns=dRoBAAABAAAAAAAAA2NkbglraW5nc3RvbmUDY29tAnR3AAAQAAE"
time="2023-08-23T23:01:34+08:00" level=debug msg="[http] sending GET request to https://freedns.controld.com:443/p1?dns=vlYBAAABAAAAAAAAA2NkbglraW5nc3RvbmUDY29tAnR3AAAFAAE"
cdn.kingstone.com.tw. 50m16s CNAME kingstonebk.azureedge.net.
kingstonebk.azureedge.net. 20m16s CNAME kingstonebk.akstd.azureedge.net.
kingstonebk.akstd.azureedge.net. 4m38s CNAME azureedge.mdc.akamaized.net.
azureedge.mdc.akamaized.net. 42m38s CNAME a1879.dscw14.akamai.net.
a1879.dscw14.akamai.net. 20s A 184.26.43.89
a1879.dscw14.akamai.net. 20s A 184.26.43.93
a1879.dscw14.akamai.net. 20s AAAA 2600:140b:2::172c:3329
a1879.dscw14.akamai.net. 20s AAAA 2600:140b:2::172c:331b

DoQ

q cdn.kingstone.com.tw -v -s quic://p1.freedns.controld.com
time="2023-08-23T23:01:44+08:00" level=debug msg="RR types: [MX TXT CNAME A AAAA NS]"
time="2023-08-23T23:01:44+08:00" level=debug msg="Using QUIC transport"
time="2023-08-23T23:01:44+08:00" level=debug msg="Dialing with QUIC ALPN tokens: [doq doq-i11]"
time="2023-08-23T23:01:45+08:00" level=debug msg="Dialing with QUIC ALPN tokens: [doq doq-i11]"
time="2023-08-23T23:01:45+08:00" level=debug msg="Dialing with QUIC ALPN tokens: [doq doq-i11]"
time="2023-08-23T23:01:45+08:00" level=debug msg="Dialing with QUIC ALPN tokens: [doq doq-i11]"
time="2023-08-23T23:01:45+08:00" level=debug msg="Dialing with QUIC ALPN tokens: [doq doq-i11]"
time="2023-08-23T23:01:45+08:00" level=debug msg="Dialing with QUIC ALPN tokens: [doq doq-i11]"
cdn.kingstone.com.tw. 50m5s CNAME kingstonebk.azureedge.net.
kingstonebk.azureedge.net. 20m5s CNAME kingstonebk.akstd.azureedge.net.
kingstonebk.akstd.azureedge.net. 4m27s CNAME azureedge.mdc.akamaized.net.
azureedge.mdc.akamaized.net. 42m27s CNAME a1879.dscw14.akamai.net.
a1879.dscw14.akamai.net. 9s A 184.26.43.89
a1879.dscw14.akamai.net. 9s A 184.26.43.93
a1879.dscw14.akamai.net. 9s AAAA 2600:140b:2::172c:3329
a1879.dscw14.akamai.net. 9s AAAA 2600:140b:2::172c:331b

DoT

q cdn.kingstone.com.tw -v -s tls://p1.freedns.controld.com
time="2023-08-23T23:01:53+08:00" level=debug msg="RR types: [A AAAA NS MX TXT CNAME]"
time="2023-08-23T23:01:53+08:00" level=debug msg="Using TLS transport"
cdn.kingstone.com.tw. 49m57s CNAME kingstonebk.azureedge.net.
kingstonebk.azureedge.net. 19m57s CNAME kingstonebk.akstd.azureedge.net.
kingstonebk.akstd.azureedge.net. 4m19s CNAME azureedge.mdc.akamaized.net.
azureedge.mdc.akamaized.net. 42m19s CNAME a1879.dscw14.akamai.net.
a1879.dscw14.akamai.net. 1s AAAA 2600:140b:2::172c:3329
a1879.dscw14.akamai.net. 1s AAAA 2600:140b:2::172c:331b
a1879.dscw14.akamai.net. 1s A 184.26.43.89
a1879.dscw14.akamai.net. 1s A 184.26.43.93

[ainar-g]

Seems to be a bug in the older quic-go. An update should fix this.

[bestpika]

Currently updated to v0.108.0-a.664+8fb76701.
Although the issues with DoQ and DoH3 have been resolved, the domain name cdn.kingstone.com.tw that I tested still cannot be queried properly. I am still receiving a bunch of NOTIMP messages.

[bestpika]

Oh, it seems to be fluctuating now, but it’s much better than it was at the beginning.

[ainar-g]

If you try a few times with 8.8.8.8, you'll see that it returns NODATA about ⅔ of the times, so my guess is that there might be issues with the authoritative servers for that domain. That likely has nothing to do with AGH.

If the original QUIC bugs are resolved, I'll close this issue, if you don't mind.