Issues with 1.1.1.1 public resolver and WARP
cloudflarestatus.com
Issues with 1.1.1.1 public resolver and WARP
1–10 of 118 posts
Re: Issues with 1.1.1.1 public resolver and WARP
#2Re: Issues with 1.1.1.1 public resolver and WARP
#3(Unaffected by this).
Found it the reverse chronological order (with timestamps being a smaller/lighter font, at least on mobile) to have caused extra thinking, which, for a status, seems undesireable.
I get wanting to expose the latest thing first, but the "top-posting" style seems intuitive. Perhaps, as a compromise, a status page would have a "Latest" block at the top, with the timestamp prominent, where the latest known status would be placed by whatever makes the updates, but the updates themselves are in the chronological order?
Re: Issues with 1.1.1.1 public resolver and WARP
#4Crazy how many things a single thing breaking takes down with it
Re: Issues with 1.1.1.1 public resolver and WARP
#5Crazy how many things a single thing breaking takes down with it
And that's why we all use more than one DNS server. Right? :-P
Re: Issues with 1.1.1.1 public resolver and WARP
#6Crazy how many things a single thing breaking takes down with it
Not sure how crazy it is when that single thing's whole business objective is to be between what you're trying to reach and yourself.
Re: Issues with 1.1.1.1 public resolver and WARP
#7Note 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 a niche hobby, but it's a fun one. I was going to suggest 9.9.9.9 aka Quad9, but apparently it comes with strings attached. https://news.ycombinator.com/item?id=16728214)
Re: Issues with 1.1.1.1 public resolver and WARP
#8Note 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…
> 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.)
Re: Issues with 1.1.1.1 public resolver and WARP
#9Note 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…
The operators of archive.* have a peculiar problem with eDNS, or rather Cloudflare’s lack of support thereof. Some details here:
https://community.cloudflare.com/t/archive-today-works-again...
Re: Issues with 1.1.1.1 public resolver and WARP
#10Note 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…
The reason has been known for a while now.