For some reason my website www.chicomputers.nl is down on a few of my devices. This website is connected to Cloudflare. using a different browser gives the same error, this happend also a month ago for a few days and then it worked again.
I also have www.chicomputers.eu that is hosted at the same provider, this one those not use Cloudflare and works fine on all my devices.
I believe Cloudflare is blocking my devices however i dont know where to look to check what might be going on.
The screenshot you shared disproves that hypothesis. You are most likely having local resolver issues. Start at layer one and work your way up. Similarly, start with the device having trouble and work your way through the entire circuit. Check its own DNS cache and move upstream.
I tryed clearing the dns cache, cloudlfare dns 1.1.1.1, removed all cookies and site permissions from all browsers (chrome, Edge and firefox).
What do you suggeted i try next?
I checked the dns settings at Cloudflare they are all correct, i did not see any errors only this in the dns queries. The spike is arround the time i started having this issue.
Enter a Command Prompt (WinKey+R) and execute the commands:
nslookup chicomputers.nl
nslookup www.chicomputers.nl
(Both will likely return the exact same set of addresses).
For each of the returned addresses, such as for example:
2001:0db8:cafe::1fd2
2001:0db8:beef::7f8d
198.51.100.200
203.0.113.100
Can you please run ping and tracert, like this:
ping 2001:0db8:cafe::1fd2
tracert 2001:0db8:cafe::1fd2
ping 2001:0db8:beef::7f8d
tracert 2001:0db8:beef::7f8d
ping 198.51.100.200
tracert 198.51.100.200
ping 203.0.113.100
tracert 203.0.113.100
And post the results?
It was not exactly meant like that:
It was not the example IP addresses I mentioned, that you should run the ping/tracert to, but the actual IP address(es) you would receive by running the nslookup command I mentioned first.
Run the nslookup command for your (sub-)domain you’re having problems with, e.g.:
From France, I see something like this:
$ nslookup chicomputers.nl
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: chicomputers.nl
Address: 188.114.97.2
Name: chicomputers.nl
Address: 188.114.96.2
Name: chicomputers.nl
Address: 2a06:98c1:3120::2
Name: chicomputers.nl
Address: 2a06:98c1:3121::2
However, some Middle Eastern / Asian locations, seems to provide (slightly) different IP addresses like this:
$ nslookup chicomputers.nl
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: chicomputers.nl
Address: 188.114.97.7
Name: chicomputers.nl
Address: 188.114.96.7
Name: chicomputers.nl
Address: 2a06:98c1:3120::7
Name: chicomputers.nl
Address: 2a06:98c1:3121::7
So therefore, it is important that you ping/tracert to all the addresses you’re finding yourself, by using the nslookup command, as you may not be seeing the same IP address(es) on your location, that I do on mine.
if I had issues from France, I would for example be running the ping/tracert command to all the four addresses:
188.114.97.2
188.114.96.2
2a06:98c1:3120::2
2a06:98c1:3121::2
But those would (given the above example) NOT be the correct ones to run them to, if I had issues from the Middle Eastern / Asian locations.
I hope it makes better sense now. 