Is 1.1.1.1 resolver having issues?
11 comments
Yes, see:
https://nitter.net/DenysVitali/status/1709476961523835246
I think there is a DNSSEC issue with the .com zone, but it's spotty (fails 75% of the time)
I think there is a DNSSEC issue with the .com zone, but it's spotty (fails 75% of the time)
https://archive.is/wTbER since cloudflarestatus.com also fails to resolve on 1.1.1.1
archive.is is not the best choice for cloudflare users.
If you are using cloudflare then archive.is links does not work anyway :D
https://jarv.is/notes/cloudflare-dns-archive-is-blocked/
If you are using cloudflare then archive.is links does not work anyway :D
https://jarv.is/notes/cloudflare-dns-archive-is-blocked/
More proof Cloudflare is a pariah
I seemed to have the issue with a .dev domain.
"Further detail will be provided as more information becomes available."
"This incident has been resolved."
I guess more information hasn't become available, even though they've apparently fixed the issue. Or did they forget they offered to give more information?
Not a fan of companies / people who just say what they think others want to hear, with no regards for actually understanding and meaning what they say.
"This incident has been resolved."
I guess more information hasn't become available, even though they've apparently fixed the issue. Or did they forget they offered to give more information?
Not a fan of companies / people who just say what they think others want to hear, with no regards for actually understanding and meaning what they say.
I guess their focus was to actually solve the issue. Now once everything is stable the people that were involved in fixing this will have the time and capacity to share what they found. I'm sure we'll see a blogpost with more details in the coming days.
CF usually posts decent RCAs of issues in post mortem.
Seems like a bad update/patch was pushed to primary resolver?
Seems like a bad update/patch was pushed to primary resolver?
Appears it’s strictly limited to 1.1.1.1
https://www.cloudflarestatus.com/incidents/j3h00yhjyw6p
CF has a secondary resolver at 1.0.0.1 which should fix the issue
My local dns resolver currently configured with 9.9.9.9 so no issues on my end.
https://www.cloudflarestatus.com/incidents/j3h00yhjyw6p
CF has a secondary resolver at 1.0.0.1 which should fix the issue
My local dns resolver currently configured with 9.9.9.9 so no issues on my end.
Our family resolves via Cloudflare's `1.1.1.3` and `1.0.0.3`. They seems to be working fine, so far.
[deleted]
yep. using 1.1.1.1 and having problems using firefox. chrome based and safari browsers seem to work okay.
edit: seems to have either gotten working again or hard refresh on browser fixed it.
edit: seems to have either gotten working again or hard refresh on browser fixed it.
The problem is intermittent.. since it's DNS related, browser caching behavior may be slightly different (also depending on your usage)
ah got it. also realized i have no idea how to check which dns i'm using out of the list i've entered.
Also have issues here (using cloudflare's 1.1.1.1)
Works for me... Maybe it just got resolved?
Same here
I thought it was my connection. Yes, I have had issues this morning.
Whats new in it
Anyone else is seeing this?