Hello!
I have been assured by my email provider (privateemail through Name Cheap)
that all of my DNS records are entered correctly but it has been 6 days and they said my records have not propagated (I also see that nothing has propagated) and they insist it is Cloudflare that needs to deal with my ticket. What should I do?
My website is thingsthatsparkjoy . com
Can you share a screenshot of the records you have created in Cloudflare?
This domain doesn’t have an MX records defined. Ensure that the account you re making DNS changes in has the following nameservers defined:
thingsthatsparkjoy.com. 86400 IN NS bonnie.ns.cloudflare.com.
thingsthatsparkjoy.com. 86400 IN NS fonzie.ns.cloudflare.com.
See also:
When I go to add the NS in Cloudflare it gives me an error message that it cant be done. This is also the only thing that shows up when I check for propagation.
Thank you. This is the error I receive when I add the NS
You are not supposed to add any NS records in Cloudflare.
Your uploaded images are not working though. Can you maybe upload them to some other site and link them here?
When you log into your dashboard do the nameserver already listed match the pair I posted? e.g. Here is an example of the nameservers assigned to one of my domains in my account. If the nameserver pair listed in your DNS tab do not match this pair you are using the wring account to manage your DNS records. If they do match then follow the tutorial I linked to crerate your MX records correctly.
I added the pics to Dropbox
(https://www.dropbox.com/sh/bc7fsrx33hfbzqr/AACXtrxPtbaVYeG58ux6RRXHa?dl=0)
Yes the correct nameservers are listed.
Just like the error in your screenshot indicates, you cannot add NS records at the apex of the zone. The absence of MX records when querying your authoritative nameservers strongly suggests that you are working in a different Cloudflare account. Can you provide a screenshot from that same account that has the assigned nameservers visible?
Thank you for your reply. The only thing I see to log into and view anything regarding Nameservers for thingsthatsparkjoy is. Note they are below the DNS records.,
(https://www.dropbox.com/sh/bc7fsrx33hfbzqr/AACXtrxPtbaVYeG58ux6RRXHa?dl=0&preview=DNS.JPG)
You are correct. I don’t know why I didn’t notice that earlier.
Have you previously used this domain with a service that may have been a Cloudflare SaaS partner?
I have literally never used this domain except to add a splash page. I have paid for email for two years that I have never been able to get to work for me. Now I need to use the site and email.
I do not know if there has been another SaaS partner involved.
I have doublechecked where I bought the Domain (hostgator) and it shows the appropriate cloudflare Nameservers.
NameCheap which manages tickets for Privateemail .com insists it is a Cloudflare issue and has not been helpful at all beyond stating the obvious that nothing has propagated.
I have included screenshots of my user panel only showing one active domain and another showing my NS are correct with the company that provided the Domain in this Dropbox folder.
[type or paste code here](https://www.dropbox.com/sh/bc7fsrx33hfbzqr/AACXtrxPtbaVYeG58ux6RRXHa?dl=0)
I’m afraid they are right, there’s absolutely nothing they can do. This is a really weird problem.
I know this will sound stupid, but have you tried deleting and recreating the MX and SPF records?
And one thing I just noticed:
In this screenshot you have an NS record. That should not be there. If you actually have that record, please delete it.
It was on my list of suggestions, too. While it may not make sense on its face, it’s still one of those things to try for reasons.
I’ll escalate this post for the attention of the Customer Support Team so they can get back to you here. If you have already contacted Support, please share your ticket number here so that they can track it.
@r.balanson If you delete the existing MX records that you created, which are
at the label thingsthatsparkjoy.com.thingsthatsparkjoy.com., and recreate them using @ as the name, you will find the results you expect.
Wait, what? I actually thought about that and doublechecked in my own settings whether I’m using @ or my full domain.
I, too, thought it looked like an @ that had been expanded in the screenshot, but the dig don’t lie.
