1.1.1.1 cannot resolve my domain but 8.8.8.8 can

DNS & Network 1.1.1.1
#1

My domain is using cloudflare CDN,the problem is suddenly happen.

about 1 or 2 days ago, 1.1.1.1 cannot resolve my domain treehing.tk , www.treehing.tk, but use 8.8.8.8 and other DNS resolver can resolve,that’s mean if my computer use 1.1.1.1,I use web browser go to my domain www.treehing.tk / treehing.tk,it fail,but if I use other resolver 8.8.8.8 (or similar),I can go to my site.

even I disabled the cloudflare CDN,the problem exist,1.1.1.1 still cannot resolve my static IP.

I’ve already tried to reflushed the DNS cache in my computer,no use for this action.

Thanks for help first.

41
螢幕截圖 2019-10-18 上午9.55.41.jpg1432×1874 533 KB

#2

Try again. I did a purge-cache for that domain at https://1.1.1.1/purge-cache/

54%20PM
Screen Shot 2019-10-17 at 7.43.54 PM.png1282×810 50.4 KB

#3

Thanks for your help,I really dunno 1.1.1.1 have a page to purge the DNS cache, but when I try again,it still have the same problem. (I used Mac & Linux terminal to try).

Do I need to run some command to update something？

42
螢幕截圖 2019-10-18 上午10.49.42.jpg3632×1084 566 KB

#4

That didn’t last long. My lookups are failing now. Contact Support. Maybe they can figure out why it’s not there.

Login to Cloudflare and then contact Cloudflare Support by clicking on the Get More Help button.

#5

Thank you.

1 Like
#6

DnsViz reports to me that they have serious trouble with .tk servers. I have too little information to throw any blame, but in general I find it a little risky to use fancy/exotic top-level domains – but I’m of course biased due to working for a ccTLD registry+operator.

#7

Well, technically .tk is a regular ccTLD as well and not an ngTLD :wink:

#8

I knew that, but being a far-away exotic ccTLD actually makes things worse than (n)gTLD, in my eyes at least… but every domain holder gets what they choose and pay for, and different people have different priorities :woman_shrugging:

#9