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

111–118 of 118 posts

Re: Issues with 1.1.1.1 public resolver and WARP

#111

Post by icedchai »

LinuxBender wrote: post #110
icedchai wrote: post #108

Earlier quoted context omitted.

Why not use the root.hints file available for this purpose? https://www.iana.org/domains/root/files Generally it is already included with most DNS servers, such as BIND.

That is useful for the initial bootstrapping but should be updated or at least validated a few times a year. If package maintainers are updating it a few times a year that works too.

Root DNS server IP's do change. However, the old ones stay active for years. Updating your root.hints a few times a year is absolutely not necessary.

Re: Issues with 1.1.1.1 public resolver and WARP

#112

Post by wlonkly »

giancarlostoro wrote: post #49
tomrod wrote: post #15

Earlier quoted context omitted.

> thus has a hardcoded exception to intentionally return bogus results to Cloudflare's resolvers. This is a bad practice.

why in the world are they doing that I wonder.

Explanation is here: https://news.ycombinator.com/item?id=36971650

Re: Issues with 1.1.1.1 public resolver and WARP

#113

Post by sambazi »

bharathyes wrote: post #37
sambazi wrote: post #29

Earlier quoted context omitted.

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

even beyond that the DNS works fine but the filtering would be turned off.

thank you for this correction to my snarky comment

Re: Issues with 1.1.1.1 public resolver and WARP

#114

Post by RockRobotRock »

drexlspivey wrote: post #109
RockRobotRock wrote: post #103

Earlier quoted context omitted.

Yeah but that's the same as a regular home DNS server that isn't recursive. Your devices also have their own cache.

The point is that if the TTL is 10mins and you lookup the domain after it expires the regular DNS will go and fetch it, unbound fetches it as soon as it expires and it is already cached

Thank you, I'm sorry I wasn't aware of the prefetch feature. That's actually pretty cool.

Re: Issues with 1.1.1.1 public resolver and WARP

#115

Post by re5i5tor »

agloe_dreams wrote: post #43
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.

A Pihole will do what you want with a ton of control added.

I run Pihole. How does it solve upstream DNS provider troubles; it still needs / uses them? I'll admit there's a lot of Pihole config I have not explored.

Re: Issues with 1.1.1.1 public resolver and WARP

#116

Post by re5i5tor »

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.

Thanks for this, really interesting.

Re: Issues with 1.1.1.1 public resolver and WARP

#117

Post by Scaevolus »

mike_d wrote: post #97
Scaevolus wrote: post #61

Earlier quoted context omitted.

Correct. Cloudflare's POP routing is quite extensive, and I'd be shocked if archive.is had more than a handful of backends it's routing to. Even so, why would an extra few dozen ms matter at all? Archive.is appears to be spindle-limited, is a client with marginally higher RTT an issue? The admin is silly. https://www.cloudflare.com/network/

Do you happen to have a mapping of Cloudflare IP space to physical POPs? To the best of my knowledge they do not publish this, which makes it quite a chore to track all their edge locations manually.

You could probably take their network map SVG and convert the circle coordinates from integer Mercator projection points to lat/lon pairs, and then map them to cities.

Re: Issues with 1.1.1.1 public resolver and WARP

#118

Post by re5i5tor »

ElongatedMusket wrote: post #47
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.

It works again, so you can go back to 1.1.1.1

Thank you, switched back and so far archive.* seems to be working on 1.1.1.1
Post reply on HN