On Fri, Apr 20, 2018 at 03:03:22PM +0000, Glenn English wrote: > On Fri, Apr 20, 2018 at 10:50 AM, Francois Gouget <fgou...@free.fr> wrote: > > > Indeed I cannot ping their DNS server (210.143.111.171) but I just > > thought they blocked ICMP. However I noticed I can in fact ping it from > > another host so I did a traceroute and the packets get blocked at the > > penultimate hop: > > > > $ traceroute -n 210.143.111.171 > > That IP, according to whois, is in Japan. And those latency numbers a > pretty big. Have you considered using a different DNS?
You misunderstand. That's not the resolver that Francois is using. It's the authoritative name server for the domain he's trying to resolve (maibokun.com). wooledg:~$ dig NS maibokun.com [...] ;; ANSWER SECTION: maibokun.com. 86400 IN NS ns3.fas.jp. maibokun.com. 86400 IN NS ns.maibokun.com. ;; ADDITIONAL SECTION: ns.maibokun.com. 163881 IN A 210.143.111.171 ns3.fas.jp. 77481 IN A 210.143.111.241 [...] As a *workaround*, sure, he could use a public resolver like Google's 8.8.8.8 as a sort of "proxy" that the Japanese name server is willing to talk to. But short of that, he is completely cut off by the router on the Japanese end.