Android device isn’t connecting to this DNS hostname(Cloudflare-dns. com) for the last few hours. It’s the only hostname supported on Android with DOH support. Is this the same for you all, could you guys check by putting this private DNS hostname in Android settings?
1 Like
Same issue here with using Cloudflare-dns[dot]com. It was working fine for the past 6-8 months until this past week.
Create a new topic, they aren’t noticing this one.
For the past 6-8 months I’ve been using Cloudflare-dns [dot] com as DoH DNS on Android 13 with no issues. This past week I noticed it stopped working with an error: Private DNS server cannot be accessed.
More screenshots:
https://i.imgur.com/XI1v2qh.png
https://i.imgur.com/7NOjZfp.png
Followed this guide saying to use cloudflare-dns[dot]com:
https://www.androidpolice.com/android-dns-over-https-mainline/
Sorry for the problems with this
Let us know if you continue to encounter this issue.
1 Like
The DNS hostname previously had connection issues, which has now resolved after the fix. However, after the fix, it lost its support for DNS over HTTPS (DoH), and now only supports DNS over TLS (DoT). It was the only DNS hostname besides Google’s that supported DoH, but now it has been downgraded to DoT, which was not the case earlier. On Android devices, it exclusively supported DoH, but due to changes made by Cloudflare after the fix, it has lost this capability.
Hi @aexsmhels, could you please share your Android version, and the exact settings you have for private DNS, we’ll try to reproduce the problem. Thanks.
2 Likes
Android version: 13
Private dns hostname: cloudflare-dns.com
If you’re testing in chrome, first turn off browser’s secure DNS setting so you’ll get the idea of how android system supports Privates DNS not the browsers. Earlier before it all happend, DNS hostname which I mentioned above used to support DoH not DoT. It seems to be a downgrade after the fix is implemented to this specific DNS hostname connection issue.
URL link for debugging: https://1.1.1.1/help#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJZZXMiLCJpc0RvaCI6Ik5vIiwicmVzb2x2ZXJJcC0xLjEuMS4xIjoiWWVzIiwicmVzb2x2ZXJJcC0xLjAuMC4xIjoiWWVzIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTExMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJZZXMiLCJkYXRhY2VudGVyTG9jYXRpb24iOiJCT00iLCJpc1dhcnAiOiJObyIsImlzcE5hbWUiOiJDbG91ZGZsYXJlIiwiaXNwQXNuIjoiMTMzMzUifQ==
1 Like
The DNS hostname ‘Cloudflare-dns(.)com’ previously had connection issues, which has now resolved after the fix. However, after the fix, it lost its support for DNS over HTTPS (DoH), and now only supports DNS over TLS (DoT). It was the only DNS hostname besides Google’s that supported DoH, but now it has been downgraded to DoT, which was not the case earlier. On Android devices, it exclusively supported DoH, but due to changes made by Cloudflare after the fix, it has lost this capability.
URL attached for debugging: https://1.1.1.1/help#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJZZXMiLCJpc0RvaCI6Ik5vIiwicmVzb2x2ZXJJcC0xLjEuMS4xIjoiWWVzIiwicmVzb2x2ZXJJcC0xLjAuMC4xIjoiWWVzIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTExMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJZZXMiLCJkYXRhY2VudGVyTG9jYXRpb24iOiJCT00iLCJpc1dhcnAiOiJObyIsImlzcE5hbWUiOiJDbG91ZGZsYXJlIiwiaXNwQXNuIjoiMTMzMzUifQ==
Hi @aexsmhels,
Thanks for the extra info. This issue is being worked on internally. By lost its support for DNS over HTTPS (DoH), how does it mean? Is there anything popping up in Android, or you mean from the 1.1.1.1 debug page, it used to have both DoH and DoT, and after the fix we applied today, it only has DoT now?
And is there any error you see from Android? Or screenshot? Thanks.
1 Like
Hi @anb,
It means that after the fix was applied, the debug page only shows support for DoT. Earlier when it was all good, it showed only DoH support not the DoT, never showed both. As also mentioned in the google security blog, Cloudflare DNS hostname ‘cloudflare-dns.com’ and google’s DNS is only supported for DoH on android. But after the recent fix, DoH support has gone, It’s DoT only. We users want the DNS hostname to work as it used to earlier, with the DoH support only not DOT.
No, not any error on android, connection issue to this DNS has been resolved. It’s just the encryption which has been degraded. Attaching link of images of how it shows now vs how it used to show earlier on the debug page:
Earlier: Imgur: The magic of the Internet
Now: Imgur: The magic of the Internet
1 Like
Thanks for the explanation @aexsmhels, that makes sense to me. Sorry about the problem, and I think we are on the same page now. Early this week, we rolled out a change which modified the IP address of domain cloudflare-dns.com, although DoH service still works fine, Android is affected somehow. We are still trying to understand the root cause behind this. I’ll post an update here once we have the issue fixed.
2 Likes
Hi @anb, thank you for understanding the matter!
Can we, as users, have a Cloudflare status page for the current DoH issue, similar to the one which was available for DoT? I don’t know why Cloudflare made status page for DoT but the issue originally was for the disconnection. Our initial complaints were regarding the disconnection issue, which was later resolved after the fix, but we then discovered that support for the DNS hostname ‘cloudflare-dns.com’ for DoH has been lost. This has been frustrating for us since other Cloudflare DNS domains on Android only support DoT. Previously, this particular DNS hostname was officially supported for DoH on Android as also stated by Google, but now it only supports DoT, which has caused dissatisfaction among users, as evidenced by various discussions on Reddit. We kindly request that Cloudflare create a status page for this issue, to keep us informed of any progress. Additionally, we would like the DNS hostname to function as it did before, with support for DoH only and not DoT. Thank you for your attention to this matter.
1 Like
We just made some changes, which brought back the previous IP for cloudflare-dns.com for now. Android clients are expected to work as before.
4 Likes
I greatly appreciate your attention and efforts on this matter, @anb! It’s now working properly, thanks!
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.