Hi everyone! I’ve replaced the CF nameservers on my host and the pending nameservers process is complete but my website is still down despite doing it correctly. Website is cineramen.gr
Attached is the screenshot of records
Kind regards
Is this supposed to be the website?
If so, the website works fine from here.
Which makes me wonder: Are you seeing an error codes or messages from your end?
If it is very recently that you made the change of name servers, you should note that the change of name servers can take 48 - 96 hours to propagate out to the whole Internet, and it may e.g. be your ISP’s DNS resolver that still has the old information cached.
Note:
The Proxy status for the A and AAAA records with the Name mail is currently set to Proxied (
).
You need to change them both to Unproxied (
) / DNS-only.
Hi @DarkDeviL and thank you for taking the time to help me out!
That is the correct website! What you just said made me sceptical and I checked out the website via mobile data and loads up just fine but If I access it on laptop via my ISP provider it outputs this error message on Chrome ‘’ This site can’t be reached
Check if there is a typo in cineramen.gr.
- If spelling is correct, [try running windows network Diagnostics](javascript:diagnoseErrors()).
Moreover, the mail records need to be unproxied? Thank you in advance, I really appreciate your help!
Forgot to add that the change took place about 2 hours ago
Yep, that NXDOMAIN error signals that the domain does not exist (e.g. that it does not have any A or AAAA records).
That is definitely not true.
Your confirmation with the above (mobile vs. laptop) confirms that it is likely your ISP’s resolver cache that still hasn’t run out yet, and is likely just a matter of patience - sometimes a few minutes may be enough, but sometimes may also take hours.
Both positive (actual DNS responses with information) and negative (e.g. NXDOMAIN / does not exist) responses are typically cached for a little while, to avoid unnecessary round trips (e.g. constant DNS queries for no good reasons).
Cloudflare’s Proxy is for HTTP (web) traffic alone, and does not proxy SMTP (email) traffic, and as such, when you are having the record that you’re pointing your MX record to, set to Proxied (), your inbound email traffic won’t flow through, as other mail servers are trying to deliver the messages to Cloudflare’s HTTP proxies, that does not listen to SMTP traffic.
Sender’s mail server may be re-trying the connection once in a while, but sender’s mail server will also give up at some point. Typically, most mail servers will re-try for ~ 120 hours (5 days), before they give up.
2 Likes
Just checked via my laptop’s ISP wifi and website running fine! Thank you so much! <3
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.