TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Issues with 1.1.1.1 public resolver in multiple locations

21 pointsby sajid11 months ago

5 comments

xnx11 months ago
Use 8.8.8.8 to switch to Google DNS.<p>Also just learned that Google has this web service <a href="https:&#x2F;&#x2F;dns.google&#x2F;" rel="nofollow">https:&#x2F;&#x2F;dns.google&#x2F;</a>
blacksmith_tb11 months ago
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.
Zekio11 months ago
that explains why I had to switch to google dns to access hacker news
stonegray11 months ago
It’s not DNS.<p>There’s no way it’s DNS.<p>It was DNS.
nevxlig11 months ago
Always a good idea to include test values to your IRR registry `whois -h rr.Level3.net 1.1.1.0&#x2F;24`