Google down every morning

Zero Trust 1.1.1.1
1

Hello - every morning this week I lose access to Google completely - cannot load any Google pages or services. This lasts for around 30 - 60 minutes. When I check downforeveryoneorjustme.com or similar services I see that it’s not just me - but the status pages for my ISP and Cloudflare all report no problems.

Is anyone else experiencing this?

2

So why you do think this is related to Cloudflare?

3

I’m using Cloudflare DNS on my router. Apologies, I should have mentioned that.

4

Because if I visit on my phone Google works, and colleagues on the same ISP don’t have this issue. I’m assuming it’s a communication issue between Cloudflare and Google, because if Google was out for a significant period of time for a significant number of users, it would be more widely reported.

This is anecdotal, for sure - but I’m network savvy, not entirely savvy with DNS troubleshooting, and when I can’t access Google I can’t lookup dig commands. :\

5

But are you actually seeing the DNS queries fail? Because the only thing Cloudflare is responsible for in that case would be converting the www.google.com query to an IP address, once that is converted it’s job done for Cloudflare.

Seeing as all other websites seem to work it’s hard to imagine it would be Cloudflare’s fault.

I’ll post the dig commands here, since you seem to be using Linux or macOS from the mention of dig:

dig google.com
dig google.com @1.1.1.1
dig google.com @8.8.8.8

dig www.google.com
dig www.google.com @1.1.1.1
dig www.google.com @8.8.8.8
6

That’s fair - I was thinking DNS because of the errors (no HTTP status errors, all name/lookup related). Thank you for the commands - it’s up again now, but I’ll check tomorrow if the same thing happens again.

I’m not assuming Cloudflare is at fault, but my colleagues all use either Google DNS or ISP DNS, and the problem doesn’t occur there.

Thanks for the guidance, I will report back with more information.

1 Like
7

I also see this every morning at around 9:15 am eastern. I think it started 3 days ago.
google.com will not resolve for a period of time, but google.ca will always work.

>kdig -d google.com @1.1.1.1
;; DEBUG: Querying for owner(google.com.), class(1), type(1), server(1.1.1.1), port(53), protocol(UDP)
;; ->>HEADER<<- opcode: QUERY; status: SERVFAIL; id: 53566
;; Flags: qr rd ra; QUERY: 1; ANSWER: 0; AUTHORITY: 0; ADDITIONAL: 0

;; QUESTION SECTION:
;; google.com.         		IN	A

;; Received 28 B
;; Time 2021-01-08 09:15:36 EST
;; From 1.1.1.1@53(UDP) in 16.2 ms
>kdig -d google.com @1.0.0.1
;; DEBUG: Querying for owner(google.com.), class(1), type(1), server(1.0.0.1), port(53), protocol(UDP)
;; ->>HEADER<<- opcode: QUERY; status: SERVFAIL; id: 44575
;; Flags: qr rd ra; QUERY: 1; ANSWER: 0; AUTHORITY: 0; ADDITIONAL: 0

;; QUESTION SECTION:
;; google.com.         		IN	A

;; Received 28 B
;; Time 2021-01-08 09:15:36 EST
;; From 1.0.0.1@53(UDP) in 34.8 ms
>kdig -d google.com @8.8.8.8
;; DEBUG: Querying for owner(google.com.), class(1), type(1), server(8.8.8.8), port(53), protocol(UDP)
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 5106
;; Flags: qr rd ra; QUERY: 1; ANSWER: 1; AUTHORITY: 0; ADDITIONAL: 0

;; QUESTION SECTION:
;; google.com.         		IN	A

;; ANSWER SECTION:
google.com.         	299	IN	A	172.217.0.238

;; Received 44 B
;; Time 2021-01-08 09:15:36 EST
;; From 8.8.8.8@53(UDP) in 51.8 ms
>dig +short CHAOS TXT id.server @1.1.1.1
"YYZ"
>dig +short CHAOS TXT id.server @1.0.0.1
"YYZ"
8

Also, in case it helps, I see this using straight ipv4 to the cloudflare dns server, and and also when using warp with a wireguard interface on linux.