Cloudflare DNS issues might affect others depending on network conditions and service status.
Cloudflare DNS issues might affect others depending on network conditions and service status.
The connection issue started after a few troubleshooting steps. It turned out the router automatically used the ISP's DNS, which resolved the problem. Are others experiencing similar issues with 1.1.1.1 and 1.0.0.1 DNS?
Execute a traceroute to 1.1.1.1 and 1.0.0.1 using your ISP's DNS servers.
The connection was interrupted briefly, but I'm using 1.1.1.1. It's unclear if this is connected.
It's back online now, thank you for your patience. I was relieved it worked after my Zoom call.
I was busy driving all day and didn’t notice what happened. My go-to DNS services were Cloudflare (1.1.1.2) and Quad9, while I previously relied on OpenDNS. Now I’m using Quad9 instead.
Not familiar with this option. Comparing speeds between Quad9 and Cloudflare is notable—your Cloudflare setup performs well even better than typical ISP connections.
In my view, ISP defaults often provide excessive tracking opportunities for your provider, potentially opening revenue streams. Cloudflare is generally my choice, though most prominent free DNS services work just fine without much impact. Some offer stronger security features or better blocking of harmful sites. OpenDNS was once better than my ISP’s DNS but became complicated. Quad9 proved faster after switching. Cloudflare and Quad9 perform similarly in speed, though real-world results can vary. I rely on both for backup purposes, ensuring a different provider if needed. A quick check showed similar resolve times across Adguard, Cloudflare, Google Public DNS, OpenDNS, and Quad9, with Cloudflare lagging slightly.