Issues with 1.1.1.1 public resolver in multiple locations

#1

Post by sajid » Thu, Jun 27, 2024, 8:21 PM UTC

Re: Issues with 1.1.1.1 public resolver in multiple locations

#2

Post by Zekio » Thu, Jun 27, 2024, 8:34 PM UTC

that explains why I had to switch to google dns to access hacker news

#3

Post by stonegray » Thu, Jun 27, 2024, 8:40 PM UTC

It’s not DNS.

There’s no way it’s DNS.

It was DNS.

#4

Post by [deleted] » Thu, Jun 27, 2024, 9:02 PM UTC

[deleted]

#5

Post by xnx » Thu, Jun 27, 2024, 9:12 PM UTC

Use 8.8.8.8 to switch to Google DNS.

Also just learned that Google has this web service https://dns.google/

#6

Post by blacksmith_tb » Thu, Jun 27, 2024, 9:14 PM UTC

For CF DNS I find 1.0.0.1 generally to work better, too many systems in past used 1.1.1.1 as a magic value.

#7

Post by nevxlig » Thu, Jun 27, 2024, 9:44 PM UTC

Always a good idea to include test values to your IRR registry `whois -h rr.Level3.net 1.1.1.0/24`