Name resolution stopped working?

Zero Trust 1.1.1.1
1

Been using it for about a year, no issue until now.

dig google.com @1.1.1.1:

; <<>> DiG 9.10.6 <<>> google.com @1.1.1.1
;; global options: +cmd
;; connection timed out; no servers could be reached

traceroute 1.1.1.1 Works fine

openssl s_client -connect 1.1.1.1:853 Works fine

What can be up?

From 1.1.1.1 debug page:

https://cloudflare-dns.com/help/#eyJpc0NmIjoiTm8iLCJpc0RvdCI6Ik5vIiwiaXNEb2giOiJObyIsInJlc29sdmVySXAtMS4xLjEuMSI6IlllcyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IkdPVCIsImlzV2FycCI6Ik5vIiwiaXNwTmFtZSI6IkJhaG5ob2YgQUIiLCJpc3BBc24iOiI4NDczIn0=
2

I know you test thoroughly, but does dig +short CHAOS TXT id.server @1.1.1.1 show anything? It resolves at LAX for me. I’m trying to think about how to figure out where Anycast sends you, though it looks like the Help page already shows GOT.

I also suppose that host google.com 1.1.1.1 uses the same mechanism.

1 Like
3

Yeah, I was routed to GOT but now I’m routed to ARN and it works again.

I guess there was something wrong with GOTs DNS resolver.

1 Like
4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.