Domain Not Verified Please add the DNS records and verify again
Mail services are unable to detect my domain despite DNS being correctly configured (services include Google workspace and GoHighLevel)
Reviewed DNS records being correctly configured
Configured DNSSEC
DNS records
You have a DNSSEC issue…
https://cf.sjr.dev/tools/check?a2a6efd1627246e8a6c03256ef9f6ff7#dns
You need to either disable DNSSEC at your registrar, or enable it at Cloudflare and copy the DS records to your registrar from your dashboard here…
https://dash.cloudflare.com/?to=/:account/:zone/dns/settings
Are you saying I cannot have DNSSEC active on both Cloudflare and Registrar, and should disable registrar’s?
You need to either disable it, or copy the DS records from Cloudflare to the registrar.
We disabled all the DNSSEC on both cloudflare and registrar, and proceeded to populate DNS and authorise records from GoHighLevel into Cloudflare.
But the propagation is still incomplete.
GoHighLevel can still not see the records from Cloudflare in their troubleshooting tools.
Can you help?
Other records are now resolving, can you show a screenshot of your Cloudflare DNS records?
Your domain status is “Setup” which means you haven’t chosen a plan, even free. (The dashboard is showing “free plan”, but “Setup” means you haven’t actually made a choice).
Go to your domain overview page and select a plan type.
If you are re-adding this domain to Cloudflare, ensure the allocated nameservers are the ones you have set at your registrar.
Just done the updates and will give it time to propagate before reaching out again.
Thank you 
You now have 4 Cloudflare nameservers set at your registrar. Only the 2 allocated ones shown at the bottom of the DNS page should be set…
https://cf.sjr.dev/tools/check?8fb5db11c5e3471294f2b2640460bb9a#whois
You need to use only the 2 shown at the bottom of your DNS page, whichever pair they are.
Either you are adding the domain to a new account, or you have removed and re-added the domain to an account. This causes Cloudflare to give you a new pair of nameservers to use.
Are those the correct ones? The DNS records you are showing resolve in daisy, not hans…
dig +short mh.maisonhaitienne.com mx @daisy.ns.cloudflare.com
20 mxb.mailgun.org.
30 mxa.mailgun.org.
dig +short mh.maisonhaitienne.com mx @hans.ns.cloudflare.com
(nothing returned)
I’m not sure, just followed your instructions.
But note that below are the Cloudflare nameservers I received after choosing my plan
Please let me know if I should replace with these instead.
Then those are the ones you need to use. You can see at the top your domain is pending. It will only go active once the nameservers are set correctly.
It seems to be working but I am now having this issue for my sub-domain in hosted with Cloudways.
Any idea how to correct this? Is it just a case of pointing the subdomain to the new nameservers in Cloudflare?
Do you have the request entry in your DNS for the deluxe hostname?
Not that I can see.
Their chat bot is suggesting adding DNS on Cloudflare for Deluxe and pointing it to the server IP.
Does that sound right to you?
