CNAME Records Not Propagating – Possible CNAME Flattening Issue
I am currently experiencing an issue with my CNAME records not propagating for my domain shifters.ch. The records in question are:
https://www.whatsmydns.net/#CNAME/mailpoet1._domainkey.shifters.ch
https://www.whatsmydns.net/#CNAME/mailpoet2._domainkey.shifters.ch
I have verified that they are correctly set up in my Cloudflare DNS settings, but they are not propagating. I was informed by MailPoet support that this might be related to CNAME Flattening or other Cloudflare security settings restricting the DNS resolution.
Could you please confirm if CNAME Flattening is affecting these records? If so, is there a way to disable it for these specific entries?
Additionally, are there any other security settings or restrictions within Cloudflare that could be preventing these CNAME records from propagating?
I would appreciate your guidance on resolving this issue.
Best regards,
DNS Propagation Checker - Global DNS Checker Tool
Instant DNS Propagation Check. Global DNS Propagation Checker - Check DNS records around the world.
6 Replies
You have nameserver records created in Cloudflare for _domainkey
;; AUTHORITY SECTION: _domainkey.shifters.ch. 300 IN NS nsany1.infomaniak.com. _domainkey.shifters.ch. 300 IN NS nsany2.infomaniak.com.You'll most likely want to just delete them.
When I remove this, the connection to the server is lost. 😦 I don't know what to do.
connection to what server? Those aren't configured to handle queries for your domain
https://shifters.ch/ When I changed it, the site went away.
I guess it's not related to that. mailpoet automatic mail delivery service overloaded the system. the server is not responding.
It's not going to be related to that error at all
Start with deleting those two ns records
For the 504
In the dashboard -> websites -> under your website, go to SSL/TLS -> Overview, make sure you're on Full Strict or Strict SSL, otherwise Click Configure and select custom -> Full (Strict)
Magic Link: https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/configuration
Start with making sure that is set. otherwise the 504 is coming from your origin
Contact your hosting provider to troubleshoot these common causes at your origin web server: Ensure the origin server responds to requests for the hostname and domain within the visitor's URL that generated the 502 or 504 error. Investigate excessive server loads, crashes, or network failures. Identify applications or services that timed out or were blocked.
thank you for your interest. you have been very helpful. i think the problem is mysql or apache service crash. i am trying to reach my server provider. we seem to have a lot to learn.