4 ms·

Is 1.1.1.1 resolver having issues?

34 points by huhtenberg 3y ago

google.com resolves fine, but www.google.com yields SERVFAIL. Anyone else is seeing this?

libco 3y ago
Same here
jadjoubran 3y ago
Also have issues here (using cloudflare's 1.1.1.1)
resbaloso 3y ago
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.
- jadjoubran 3y ago
  The problem is intermittent.. since it's DNS related, browser caching behavior may be slightly different (also depending on your usage)
  - resbaloso 3y ago
    ah got it. also realized i have no idea how to check which dns i'm using out of the list i've entered.
denysvitali 3y ago
Yes, see: https://nitter.net/DenysVitali/status/1709476961523835246 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)
- denysvitali 3y ago
  Confirmed: https://www.cloudflarestatus.com/incidents/j3h00yhjyw6p https://www.cloudflarestatus.com/incidents/j3h00yhjyw6p
  - huhtenberg 3y ago
    https://archive.is/wTbER https://archive.is/wTbER since cloudflarestatus.com also fails to resolve on 1.1.1.1
    - sccxy 3y ago
      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/ https://jarv.is/notes/cloudflare-dns-archive-is-blocked/
      - warrenm 3y ago
        More proof Cloudflare is a pariah
- frou_dh 3y ago
  I seemed to have the issue with a .dev domain.
deleted 3y ago
[deleted]
Beinglis23 3y ago
Whats new in it
g232089 3y ago
I thought it was my connection. Yes, I have had issues this morning.
johnklos 3y ago
"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.
- fundatus 3y ago
  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.
- xyst 3y ago
  CF usually posts decent RCAs of issues in post mortem. Seems like a bad update/patch was pushed to primary resolver?
xyst 3y ago
Appears it’s strictly limited to 1.1.1.1 https://www.cloudflarestatus.com/incidents/j3h00yhjyw6p 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.
Brajeshwar 3y ago
Our family resolves via Cloudflare's `1.1.1.3` and `1.0.0.3`. They seems to be working fine, so far.
mdwalters 3y ago
Works for me... Maybe it just got resolved?

34 points by huhtenberg 3y ago

google.com resolves fine, but www.google.com yields SERVFAIL. Anyone else is seeing this?

libco 3y ago

Same here

jadjoubran 3y ago

Also have issues here (using cloudflare's 1.1.1.1)

resbaloso 3y ago

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.

jadjoubran 3y ago
The problem is intermittent.. since it's DNS related, browser caching behavior may be slightly different (also depending on your usage)
- resbaloso 3y ago
  ah got it. also realized i have no idea how to check which dns i'm using out of the list i've entered.

denysvitali 3y ago

Yes, see: https://nitter.net/DenysVitali/status/1709476961523835246 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)

denysvitali 3y ago
Confirmed: https://www.cloudflarestatus.com/incidents/j3h00yhjyw6p https://www.cloudflarestatus.com/incidents/j3h00yhjyw6p
- huhtenberg 3y ago
  https://archive.is/wTbER https://archive.is/wTbER since cloudflarestatus.com also fails to resolve on 1.1.1.1
  - sccxy 3y ago
    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/ https://jarv.is/notes/cloudflare-dns-archive-is-blocked/
    - warrenm 3y ago
      More proof Cloudflare is a pariah
frou_dh 3y ago
I seemed to have the issue with a .dev domain.

deleted 3y ago

[deleted]

Beinglis23 3y ago

Whats new in it

g232089 3y ago

I thought it was my connection. Yes, I have had issues this morning.

johnklos 3y ago

"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.

fundatus 3y ago
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.
xyst 3y ago
CF usually posts decent RCAs of issues in post mortem. Seems like a bad update/patch was pushed to primary resolver?

xyst 3y ago

Appears it’s strictly limited to 1.1.1.1 https://www.cloudflarestatus.com/incidents/j3h00yhjyw6p 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.

Brajeshwar 3y ago

Our family resolves via Cloudflare's `1.1.1.3` and `1.0.0.3`. They seems to be working fine, so far.

mdwalters 3y ago

Works for me... Maybe it just got resolved?