maas-events.nl
Cloudflare not responding with DNS lookups, after moving domain to the correct nameservers
DNS not responding/updating
You’re using a self-signed SSL certificate on your origin host which has expired 277 days ago.
You’d have to double-check and renew your SSL certificate using Plesk panel for your domain name before either un-pausing Cloudflare or enabling the proxy 
for your DNS records.
Only then, when your website responds over HTTPS, you should either switch back to or un-pause Cloudflare and double-check your SSL/TLS setting to make sure it’s Full (Strict).
You’re not understanding me.
When i try to ping the server i get a DNS server not found, same as all other DNS requests
Since you’re recently changed domain servers to Cloudflare this might be temporary due to the DNS propagation time and your local ISP cache:
$ nslookup maas-events.nl
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
Name: maas-events.nl
Address: 31.xxx.xxx.x -> masking here to not share publicly on the forums
Domain nameservers:
ben.ns.cloudflare.com
kristin.ns.cloudflare.com
$ ping maas-events.nl
Pinging maas-events.nl [31.xxx.xxx.x] with 32 bytes of data:
Reply from 31.xxx.xxx.x: bytes=32 time=28ms TTL=52
Reply from 31.xxx.xxx.x: bytes=32 time=28ms TTL=52
Reply from 31.xxx.xxx.x: bytes=32 time=28ms TTL=52
Reply from 31.xxx.xxx.x: bytes=32 time=28ms TTL=52
Ping statistics for 31.204.147.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 28ms, Average = 28ms
I can see your Website, but only over HTTP and with self-signed SSL certificate.
Hmm. That is weird. When i tried to DIG through cloudflare’s nameservers, they wouldn’t give me any results. Right now it seems to be propegating, but I don’t understand why it took cloudflare so long
Regular DNS propagation time might take up to 24h or a bi longer.
Not quite due to the Cloudflare, rather the TTL set on your domain registrar to keep the old domain nameservers and about the TTL from old DNS provider such as Web hosting (which are mostly using cPanel, Plesk …).
Restart your router, or flush your local DNS cache at your device.
Or, try by using some other provider, such as mobile data on your mobile device, or maybe using a VPN, or set custom DNS servers for your device to some other.
No matter what, it’ll work soon if not already 
I understand that, but it even did not send any response whenever i specifically asked cloudflare’s nameservers what the DNS records were. Strange
Like below dig command or something else? 
$ dig A maas-events.nl @1.1.1.1
At the end, don’t forget to select correctly SSL settings under the SSL/TLS tab of Cloudflare dashboard, otherwise you’d experience some redirection issues and errors such as 525, etc. once the DNS records are proxied .
Yes exactly that! That’s why i was so confused
Weird, if so
Might be temporary something “in-the-air”, otherwise I am not sure.
However, thank you for feedback about it.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.