Cloudflare: Is anyone else seeing DNS outages? • Hacker News Board

Re: Cloudflare: Is anyone else seeing DNS outages?

#31

Post by amishkin » Fri, Jul 17, 2020, 9:31 PM UTC

Yep, all my sites went down for a bit.

Re: Cloudflare: Is anyone else seeing DNS outages?

#32

Post by jyrkesh » Fri, Jul 17, 2020, 9:31 PM UTC

1f60c wrote: post #23

arh68 wrote: post #16

Well I just rebooted my modem, but modem + router checked out (I know the IPs). Rebooted the Pi-Hole, seems to be back up now. Cloudflare is the only DNS my Pi-Hole forwards to. I think I will add another, now..

Which ones are you going to add? Just curious. :)

I've used 4.2.2.1 extensively in the past, and never had any issues. 4.2.2.1 through 4.2.2.6 are run by Level 3

Re: Cloudflare: Is anyone else seeing DNS outages?

#33

Post by SwiftyBug » Fri, Jul 17, 2020, 9:32 PM UTC

sashk wrote: post #14

Yep, github actions failing because of this too.

All my tests passed. The only explanation must be because Github Actions is being affected. My tests would never pass otherwise.

Re: Cloudflare: Is anyone else seeing DNS outages?

#34

Post by christoph » Fri, Jul 17, 2020, 9:32 PM UTC

nbevans wrote: post #13

oxfordmale wrote: post #11

Yes, experiencing the same issue from the UK.

And me. (UK)

Same (UK) some sites work, some others not. Thought it was just me.

Re: Cloudflare: Is anyone else seeing DNS outages?

#35

Post by NickLamp » Fri, Jul 17, 2020, 9:33 PM UTC

benatkin wrote: post #18

I can't get to chess.com.

Lichess is up (and also better)

Re: Cloudflare: Is anyone else seeing DNS outages?

#36

Post by ricardonunez » Fri, Jul 17, 2020, 9:34 PM UTC

My websites are down. I noticed when some CDNs were down.

Re: Cloudflare: Is anyone else seeing DNS outages?

#37

Post by 1f60c » Fri, Jul 17, 2020, 9:36 PM UTC

jyrkesh wrote: post #32

1f60c wrote: post #23

Earlier quoted context omitted.

Which ones are you going to add? Just curious. :)

I've used 4.2.2.1 extensively in the past, and never had any issues. 4.2.2.1 through 4.2.2.6 are run by Level 3

Oh, I've heard about it, but I don't like to use it because it returns a search page filled with ads for nonexistent domains.

Re: Cloudflare: Is anyone else seeing DNS outages?

#38

Post by ed25519FUUU » Fri, Jul 17, 2020, 9:37 PM UTC

I'm realizing how bad the experience is when my computer starts falling back to the "secondary" DNS. It adds a little over 1s latency to resolutions (very noticable).

I wish my computer was smart enough to "healthcheck" the primary and secondary, and fallback to using the secondary as the primary until it becomes healthy again.

Re: Cloudflare: Is anyone else seeing DNS outages?

#39

Post by nurettin » Fri, Jul 17, 2020, 9:39 PM UTC

nathanaldensr wrote: post #20

$ dig @1.1.1.1 google.com ; > DiG 9.11.5-P4-5.1+deb10u1-Raspbian > @1.1.1.1 google.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig @1.0.0.1 google.com ; > DiG 9.11.5-P4-5.1+deb10u1-Raspbian > @1.0.0.1 google.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached

$ dig @1.1.1.1 google.com

; > DiG 9.11.20-RedHat-9.11.20-1.fc32 > @1.1.1.1 google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;google.com. IN A

;; ANSWER SECTION: google.com. 249 IN A 216.58.206.174

;; Query time: 9 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Sat Jul 18 00:38:35 +03 2020 ;; MSG SIZE rcvd: 65

Re: Cloudflare: Is anyone else seeing DNS outages?

#40

Post by ed25519FUUU » Fri, Jul 17, 2020, 9:41 PM UTC

nathanaldensr wrote: post #20

$ dig @1.1.1.1 google.com ; > DiG 9.11.5-P4-5.1+deb10u1-Raspbian > @1.1.1.1 google.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig @1.0.0.1 google.com ; > DiG 9.11.5-P4-5.1+deb10u1-Raspbian > @1.0.0.1 google.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached

Both the primary and the secondary going down is a killer. It's enough to make me switch out the secondary to a non-cloudflare DNS.

Even when the secondary works the performance is pretty miserable. Adds about a 1s latency to each DNS resolution while it wait's for the primary to fail.