Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Issues with 1.1.1.1 public resolver and WARP

cloudflarestatus.com

Post reply on HN
Print view View original

21–30 of 118 posts

Re: Issues with 1.1.1.1 public resolver and WARP

#21

Post by marban »

mhitza wrote: post #17
sillysaurusx wrote: post #7

Note that if you use 1.1.1.1, you apparently can't visit archive.is links. I'm not sure why, but around a dozen people on HN have confirmed this. (At least as of a couple months ago.) I think the world could use more alternatives to 8.8.8.8. Hopefully 1.1.1.1 will become more reliable as the years tick by. (Do you use something besides 8.8.8.8 or 1.1.1.1? If so, post it here! Collecting reliable DNS servers might be…

I use https://www.dns0.eu/ but that doesn't have a fancy IP address

Any benchmarks or experiences over CF from Europe?

Re: Issues with 1.1.1.1 public resolver and WARP

#22

Post by mtsr »

dano wrote: post #19
re5i5tor wrote: post #11

Earlier quoted context omitted.

Switched off 1.1.1.1 for that reason a while back. Currently using OpenDNS which is now unfortunately owned by Cisco. Definitely a lack of actually open alternatives.

Running your own resolver that points directly to root servers is also an option. https://nlnetlabs.nl/projects/unbound/about/ It isn't too complicated to set up and provides faster responses than external DNS servers, especially after the cache gets built up a bit.

Indeed, this is my preferred solution too. Unfortunately this doesn’t protect one from snooping by network intermediaries, although that’s much less of an issue in the EU due to privacy regulations. At least in principle, but it’s hard to be sure.

Re: Issues with 1.1.1.1 public resolver and WARP

#23

Post by quesera »

Just a reminder for anyone on the fence, or who has not considered it previously...

Running your own DNS resolver is super easy. It probably has the highest ROI of any self-hosted service, because it is so easy and inexpensive to do.

I recommend Unbound: https://nlnetlabs.nl/projects/unbound

Re: Issues with 1.1.1.1 public resolver and WARP

#26

Post by yakubin »

re5i5tor wrote: post #11
sillysaurusx wrote: post #7

Note that if you use 1.1.1.1, you apparently can't visit archive.is links. I'm not sure why, but around a dozen people on HN have confirmed this. (At least as of a couple months ago.) I think the world could use more alternatives to 8.8.8.8. Hopefully 1.1.1.1 will become more reliable as the years tick by. (Do you use something besides 8.8.8.8 or 1.1.1.1? If so, post it here! Collecting reliable DNS servers might be…

Switched off 1.1.1.1 for that reason a while back. Currently using OpenDNS which is now unfortunately owned by Cisco. Definitely a lack of actually open alternatives.

I used to use OpenDNS, but then out of nowhere they decided to enable parental control by default[1] and without an account I don’t think I could disable it.

[1]: Maybe only in EU?

Re: Issues with 1.1.1.1 public resolver and WARP

#27

Post by SSLy »

lopkeny12ko wrote: post #24

What's the point of having a secondary endpoint 1.0.0.1 if an outage breaks both that and 1.1.1.1? Are these two servers not running in physically isolated regions with independent code deploys?

DNS servers are run anycast from each cloudflare POP. Why are the two addresses' fault domains not separated otherwise is the proper question.

Re: Issues with 1.1.1.1 public resolver and WARP

#28

Post by lantry »

quesera wrote: post #23

Just a reminder for anyone on the fence, or who has not considered it previously... Running your own DNS resolver is super easy. It probably has the highest ROI of any self-hosted service, because it is so easy and inexpensive to do. I recommend Unbound: https://nlnetlabs.nl/projects/unbound

Plus you can do fun things like block ads across your whole network with tools like pihole.

Re: Issues with 1.1.1.1 public resolver and WARP

#29

Post by sambazi »

shasts wrote: post #18
sillysaurusx wrote: post #7

Note that if you use 1.1.1.1, you apparently can't visit archive.is links. I'm not sure why, but around a dozen people on HN have confirmed this. (At least as of a couple months ago.) I think the world could use more alternatives to 8.8.8.8. Hopefully 1.1.1.1 will become more reliable as the years tick by. (Do you use something besides 8.8.8.8 or 1.1.1.1? If so, post it here! Collecting reliable DNS servers might be…

There is https://www.dns0.eu and https://nextdns.io . I like the 300K requests per month free tier that nextdns.io has. Comes with plenty of filters.

like i ever wanted to care about the number of dns-requests originating from my systems.

Re: Issues with 1.1.1.1 public resolver and WARP

#30

Post by Jnr »

sillysaurusx wrote: post #7

Note that if you use 1.1.1.1, you apparently can't visit archive.is links. I'm not sure why, but around a dozen people on HN have confirmed this. (At least as of a couple months ago.) I think the world could use more alternatives to 8.8.8.8. Hopefully 1.1.1.1 will become more reliable as the years tick by. (Do you use something besides 8.8.8.8 or 1.1.1.1? If so, post it here! Collecting reliable DNS servers might be…

How come archive.is works for me?

I have set up Cloudflare DoH in my router, I block other popular DoH servers on my network and I also redirect any other DNS queries (UDP 53) to my router's DNS (which in turn uses Cloudflare).

And at least in my region (EU) I did not notice any issues with 1.1.1.1.

Post reply on HN