|
Title: Cloudflare: Origin DNS error Post by: ABCbits on April 19, 2019, 06:54:57 PM I was browsing and few times i encountered Cloudflare error with this message (Ray ID and IP removed due to privacy reason).
Quote Error 1016 Origin DNS error What happened? You've requested a page on a website (bitcointalk.org) that is on the Cloudflare network. Cloudflare is currently unable to resolve your requested domain (bitcointalk.org). What can I do? If you are a visitor of this website: Please try again in a few minutes. If you are the owner of this website: Check your DNS settings. If you are using a CNAME origin record, make sure it is valid and resolvable. Additional troubleshooting information here. Did anyone encounter same problem? For reference, i'm using Tor connection. Title: Re: Cloudflare: Origin DNS error Post by: theymos on April 19, 2019, 07:58:17 PM I see nothing that would cause that on my end. The main possibility which comes to my mind is: Tor gets its DNS from a random semi-untrusted Tor exit node, and it gave you a Cloudflare IP for bitcointalk.org, but the wrong one, possibly as part of some attack (though this would seem to require a flaw on Cloudflare's end), or possibly due to some weird network conditions at the exit node. It could also just be a Cloudflare hiccup.
Title: Re: Cloudflare: Origin DNS error Post by: Vod on April 19, 2019, 07:59:35 PM Did anyone encounter same problem? For reference, i'm using Tor connection. I get this every now and then... I just refresh the page in a few secs or mins. Title: Re: Cloudflare: Origin DNS error Post by: jackg on April 20, 2019, 12:10:16 AM Did anyone encounter same problem? For reference, i'm using Tor connection. I get this every now and then... I just refresh the page in a few secs or mins. I'm guessing just making a new identity might work too. I haven't used tor in a while but I imagine Theymos has it right. If there's a way to configure the dns I think 1.1.1.1 is said to have encrypted dns so it should make it more secure if you can use it over tor (it could also be that the cache for the dns of that exit node hasn't refreshed itself recently). |