F5F Stay Refreshed Power Users Networks Check if Cloudflare DNS 1.1.1.1 is operational.

Check if Cloudflare DNS 1.1.1.1 is operational.

Check if Cloudflare DNS 1.1.1.1 is operational.

Pages (2): 1 2 Next
S
ShadowWolf920
Junior Member
9
03-11-2024, 01:35 PM
#1
Could be. Also trying Cloudflare DNS, but I'm running into problems too
S
ShadowWolf920
03-11-2024, 01:35 PM #1

Could be. Also trying Cloudflare DNS, but I'm running into problems too

X
xTripleMinerx
Posting Freak
846
03-11-2024, 08:30 PM
#2
They seem to be indicating a service disruption, curious about the reason https://www.cloudflarestatus.com/
X
xTripleMinerx
03-11-2024, 08:30 PM #2

They seem to be indicating a service disruption, curious about the reason https://www.cloudflarestatus.com/

A
alejandro351
Member
137
03-18-2024, 09:04 AM
#3
I also reverted to auto DNS and it's working properly now.
A
alejandro351
03-18-2024, 09:04 AM #3

I also reverted to auto DNS and it's working properly now.

W
WF_Catt
Posting Freak
761
03-19-2024, 02:48 AM
#4
Visit the site to check Cloudflare's status and performance.
W
WF_Catt
03-19-2024, 02:48 AM #4

Visit the site to check Cloudflare's status and performance.

L
llTheCubixll
Junior Member
5
04-04-2024, 02:16 PM
#5
I wasn't able to reach any DNS servers—no DNS data arrived at all—but routing stayed intact with IP addresses. I switched from Cloudflare to Google (using /flushdns) and then to OpenDNS, but both returned no response. After rebooting my computer and testing on a Mac that only uses Google DNS, the issue disappeared. I also rebooted my router, which now routes me through a different path and restored full DNS access. It seems there was some unusual redirection of popular DNS traffic, which could reveal detailed browsing patterns for many users.
L
llTheCubixll
04-04-2024, 02:16 PM #5

I wasn't able to reach any DNS servers—no DNS data arrived at all—but routing stayed intact with IP addresses. I switched from Cloudflare to Google (using /flushdns) and then to OpenDNS, but both returned no response. After rebooting my computer and testing on a Mac that only uses Google DNS, the issue disappeared. I also rebooted my router, which now routes me through a different path and restored full DNS access. It seems there was some unusual redirection of popular DNS traffic, which could reveal detailed browsing patterns for many users.

T
Telux
Junior Member
40
04-04-2024, 08:43 PM
#6
It seems odd. I managed to change settings and restart without any problems.
T
Telux
04-04-2024, 08:43 PM #6

It seems odd. I managed to change settings and restart without any problems.

E
Ender_Craft47
Posting Freak
866
04-13-2024, 05:02 PM
#7
System appears operational. Connection restored via Wi-Fi on device.
E
Ender_Craft47
04-13-2024, 05:02 PM #7

System appears operational. Connection restored via Wi-Fi on device.

J
Joris_boef
Member
51
04-13-2024, 07:31 PM
#8
It was incredibly quick. Checking the status page shows their DNS timeouts and the implementation of the fix are just a second apart... 0_0
J
Joris_boef
04-13-2024, 07:31 PM #8

It was incredibly quick. Checking the status page shows their DNS timeouts and the implementation of the fix are just a second apart... 0_0

B
Butterfly1416
Senior Member
701
04-14-2024, 01:30 AM
#9
I performed a traceroute to 1.1.1.1 (Cloudflare public DNS), 8.8.8.8 (Google public DNS) and 208.67.222.222 (OpenDNS public DNS). The paths changed significantly before and after I rebooted my router. I would have liked to save this information, but I restarted the machine after testing but before rebooting the router. It would have been fascinating to see.
B
Butterfly1416
04-14-2024, 01:30 AM #9

I performed a traceroute to 1.1.1.1 (Cloudflare public DNS), 8.8.8.8 (Google public DNS) and 208.67.222.222 (OpenDNS public DNS). The paths changed significantly before and after I rebooted my router. I would have liked to save this information, but I restarted the machine after testing but before rebooting the router. It would have been fascinating to see.

C
Coudz
Junior Member
13
04-14-2024, 09:40 AM
#10
In Windows you could have simply configured the main DNS to 1.1.1.1 and the backup to your ISP’s DNS instead of relying on Cloudflare. This way, if the service fails you’d still maintain network access. (Or even better, set up multiple static DNS entries in your router—DD-WRT supports three: 1.0.0.1 (Cloudflare), 8.8.8.8 (Google) and your ISP’s.)
C
Coudz
04-14-2024, 09:40 AM #10

In Windows you could have simply configured the main DNS to 1.1.1.1 and the backup to your ISP’s DNS instead of relying on Cloudflare. This way, if the service fails you’d still maintain network access. (Or even better, set up multiple static DNS entries in your router—DD-WRT supports three: 1.0.0.1 (Cloudflare), 8.8.8.8 (Google) and your ISP’s.)

Pages (2): 1 2 Next