[GH-ISSUE #14] Can't use RethinkDNS filtered DoH addresses #11

New issue

Closed

opened 2026-03-14 01:03:18 +03:00 by kerem · 4 comments

kerem commented

2026-03-14 01:03:18 +03:00

Owner

Originally created by @tina-hello on GitHub (May 10, 2021).
Original GitHub issue: https://github.com/ameshkov/dnslookup/issues/14

Unfiltered DoH address such as

https://basic.rethinkdns.com/

and

https://basic.rethinkdns.com/dns-query/

works, but

https://basic.rethinkdns.com/dns-query/1:AMD_PwDw

such as configured by https://rethinkdns.com/configure#1:AMD_PwDw doesn't work with the error message:

Cannot make the DNS request: dns: id mismatch

The filtered URL works with Chrome. This isn't simply because of the character, since

https://dns.nextdns.io/1:AMD_PwDw

works. So this seems to be a quirk on how either the dnslookup or RethinkDNS (which is based on Cloudflare Worker) send the query.

Originally created by @tina-hello on GitHub (May 10, 2021). Original GitHub issue: https://github.com/ameshkov/dnslookup/issues/14 Unfiltered DoH address such as https://basic.rethinkdns.com/ and https://basic.rethinkdns.com/dns-query/ works, but https://basic.rethinkdns.com/dns-query/1:AMD_PwDw such as configured by https://rethinkdns.com/configure#1:AMD_PwDw doesn't work with the error message: `Cannot make the DNS request: dns: id mismatch` The filtered URL works with Chrome. This isn't simply because of the character, since https://dns.nextdns.io/1:AMD_PwDw works. So this seems to be a quirk on how either the dnslookup or RethinkDNS (which is based on Cloudflare Worker) send the query.

kerem closed this issue

2026-03-14 01:03:24 +03:00

kerem commented

2026-03-14 01:03:29 +03:00

Author

Owner

@ameshkov commented on GitHub (May 10, 2021):

This looks more like a bug of RethinkDNS that returns responses with the wrong DNS ID.

@ignoramous could you please take a look?

@ameshkov commented on GitHub (May 10, 2021): This looks more like a bug of RethinkDNS that returns responses with the wrong DNS ID. @ignoramous could you please take a look?

kerem commented

2026-03-14 01:03:34 +03:00

Author

Owner

@tina-hello commented on GitHub (May 10, 2021):

Yeah I just tested the URL against https://dohjs.org/, they don't work with GET, but work with POST. While Chrome seems to only use POST for DoH calls, the standards actually include both GET & POST, I guess both dnslookup and AdGuard Home (at least the test stream) use GET instead?

@tina-hello commented on GitHub (May 10, 2021): Yeah I just tested the URL against https://dohjs.org/, they don't work with GET, but work with POST. While Chrome seems to only use POST for DoH calls, the standards actually include both GET & POST, I guess both dnslookup and AdGuard Home (at least the test stream) use GET instead?

kerem commented

2026-03-14 01:03:39 +03:00

Author

Owner

@ameshkov commented on GitHub (May 10, 2021):

We use GET for a reason, it's better from the performance point of view (POST implementation in golang is a bit messy).

@ameshkov commented on GitHub (May 10, 2021): We use GET for a reason, it's better from the performance point of view (POST implementation in golang is a bit messy).

kerem commented

2026-03-14 01:03:45 +03:00

Author

Owner

@ignoramous commented on GitHub (May 11, 2021):

@ameshkov Tracking it here: https://github.com/serverless-dns/serverless-dns/issues/2

GET was once disabled due to bots, forgot to enable it back again.

Thanks!

@ignoramous commented on GitHub (May 11, 2021): @ameshkov Tracking it here: https://github.com/serverless-dns/serverless-dns/issues/2 `GET` was once disabled due to bots, forgot to enable it back again. Thanks!