ozo
1
sandro
2
Can you post the output of the following commands?
curl -v 'https://1.1.1.1/dns-query?ct=application/dns-json&name=cloudflare.com'
curl -v 'https://1.0.0.1/dns-query?ct=application/dns-json&name=cloudflare.com'
However AFAIK there currently are some issues with DoH in YYZ, so it probably is best if you go straight for a support ticket.
ozo
3
Thanks Sandro,
Cannot post more than 2 links as a new user, here’s the end of the output:
…
GET /dns-query?ct=application/dns-json&name=cloudflare.com HTTP/2
Host: 1.1.1.1
User-Agent: curl/7.64.1
Accept: /
- Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 400
< date: Sun, 08 Dec 2019 16:12:40 GMT
< content-length: 0
< access-control-allow-origin: *
< expect-ct: max-age=604800, report-uri=“https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct”
< server: cloudflare
< cf-ray: 542005ae8e61caa4-YYZ
<
- Connection #0 to host 1.1.1.1 left intact
- Closing connection 0
sandro
4
Yes, still seems to be the same issue.
Definitely a case for a support ticket, best to [email protected] and reference the thread here as well.
@cloonan
Hi, the ‘ct=application/dns-json’ was deprecated in one of the draft versions. 1.1.1.1 supports the latest RFC 8484: DNS Queries over HTTPS (DoH) version. See Using JSON · Cloudflare 1.1.1.1 docs for the format reference. I’m not sure if Brave supports RFC8484 or some older draft perhaps?
ozo
6
I have posted a question to Brave community. Waiting for the updates.
sandro
7
That shouldnt be the reason for the issue though. There have been a few reports recently about DoH issues in YYZ.
Also, Have problems with 1.1.1.1? *Read Me First* would need an update in this case.