This site can’t be reached - very frustrating



So when i try to access my website from my home computer, i get an error saying:
“This site can’t be reached took too long to respond.
Search Google for ynet center co il

The wired thing is from my mobile device it works fine. Also seems like third party website are able to access it. Tried everything but can’t get it to work. My IP is white-listed BTW.

Would appreciate any advice.


The site seems to be properly configured and it works on as well.

The error message looks like a standard Chrome message and that might hint that it cant even reach Cloudflare. Could it be a local problem in that case?


Thank you Sandro.

Internet connection is good and everything else works perfectly well. Just this site won’t load for me. Tried from a desktop an my laptop too. From different browsers also.


Do you have an entry in your hosts file poiting to a different IP?


run an nsllookup on your domain to verify that it shows cloudflare IPs

ipconfig /flushdns is worth a try too.


Never messed around with the hosts file so i guess that’s not it.

Did flushdns as you suggested. got the message saying: “Successfully flushed the DNS Resolver Cache.”

Still same problem though :confused:


Wha’ts the result of


Which DNS servers are used in your network?


Just a remark, that would not take into account any possible hosts overrides but go straight for DNS. ping is usually a good way to check in that case as that will resolve via hosts too.


Server: Broadcom

Non-authoritative answer:


Pinging [] with 32 bytes of data:
Request timed out.


This is not a Cloudflare IP.

inetnum: -
descr: Yediot Technologies

it should look like

:~$ nslookup

Non-authoritative answer:

please repeat this with.


If you get a similar reusult than mine above plese check your nameserver,
flush it’s cache if you have added your page or the records recently (past 48 hours) or wait a bit. :slight_smile:



Are you asking him to hack into his ISP’s infrastructure? :wink:


Hell no :joy:

But his router eventually if it has a cache.

Server: Broadcom

(btw: the DNS adress is why I pointed to Google DNS instead of CF DNS Servers /

Or change the nameservers on it. How ever something is wrong with the name resolution within the local network or the upstream DNS returns a wrong record. For whatever the reason is. Lets hope itÄs only cached and not blocked by someone / something)


Good point, I completely ignored the bit of him posting an nslookup with a private server :blush:


That’s what i got:

Non-authoritative answer:
Addresses: 2400:cb00:2048:1::681b:a8b7


Sorry, got a bit confused from the answers here. nameservers been updated about two week ago.
What can do then?


There is something wrong with your name resolution within your (home?) network. This could have serveral reasons: Your local DNS servers

  • blocked your request (through your ISP, possibly due to local law)
  • servers don’t work (correctly)
  • are misconfigured

Your local DNS, or the DNS that is used by your internet router) returns a wrong IP (
Your second try against the Google Nameservers ( returned the correct entries:

Non-authoritative answer:
Addresses: 2400:cb00:2048:1::681b:a8b7

Quick fix:
Change your nameservers on your systems to google ( and


Thanks Mark.

Can you please point me to where should i apply this change?


There you go


It worked! Thanks everybody for you help!

closed #20

This topic was automatically closed after 14 days. New replies are no longer allowed.