I added a custom domain 2 days ago to my CF Pages site, and my CNAME records have not propagated yet
I've been learning a new stack with deployment using Cloudflare Pages, and earlier this week I applied a custom domain so I could test out the MailChannel plugin.
I bought my domain from Cloudflare, applied it to my Pages site, and it automatically created the zone and some DNS records.
I created some more records for the plugin and have been troubleshooting the last couple days.
I checked my DNS record propagation using https://dnschecker.org and it seems my CNAME record isn't detected yet. I also created 2 TXT records for MailChannel, and only 1 of them appears and seems to propagate really fast when updated.
I also set up CF Email Routing which added some MX records and those also propagate nearly immediately.
I'm pretty new to DNS so idk if some records are just faster than others, or maybe I missed a step in applying my custom domain.
I provided a pic of my CNAME records, the custom domains tab, and the result from dnschecker.org.
lmk if I can provide anything else, thank you
18 Replies
Because they are proxied, Cloudflare responds with their A/AAAA Proxy IPs rather then the raw CNAME, and resolves the CNAME internally
(In other words, use A/AAAA types and you can see your website resolves fine, and that is expected behavior)
The site works fine for me, are you having an issue with the site itself, or just confused why you couldn't resolve the CNAME directly?
What's the TXT Record that is not showing (showing it in the dashboard would be helpful)
here's my full DNS Records, the TXT I'm referring to is
_mailchannels subdomain
DNS over Discord: TXT records
_mailchannels.justenfalk.com TXT @1.1.1.1 +noall +answer
diggy diggy hole
hmm, in what way do you not see it?
It may be worth noting, if you're trying to send mail from a function, I believe you'll need to whitelist your pages.dev
It might be a miscommunication from MailChannel support, they replied they did not see the TXT record when querying my domain, and that once it resolved it would work.
I see it now, didn't realize I would need to check the specific subdomain instead of the apex to see it
What error are you getting with mailchannels?
if it's a simple whitelist issue, it should tell you the domain to add (in the error response)
It returns a 512 response when I look at the logs for the Function when I run it, along with this message
ahhh it looks like the plugin just swallows the error message
try changing your CF ID to your pages.dev domain rather then your workers.dev, and try in a bit (give it a few mins to update, not sure if they cache it or not)
i.e change it to cv-cms.pages.dev
ok so use the CF domain and not my custom domain?
I mean modifying the mailchannels txt rrecord you created to
ahh ok thought you meant change the subdomain of my workers
yea ignore that. They're using the Cf-Worker header, which is what matters.
The CF-Worker header is the zone the worker is executing on.
If it was a worker on workers.dev, then your worker.dev would be right.
If it was a worker on a custom domain, then the custom domain zone would be right.
Pages is special, and I believe all functions always count as executing on your pages.dev zone, so I would try that.
Yay! Thank you!
Now to work on DKIM
I did have one lingering question about the custom domain - will the app domain (cv-cms.pages.dev) always be exposed or, should I make some sort of record in case someone finds that url and redirect them to my custom domain?
You can use Bulk Redirects for the pages.dev itself: https://developers.cloudflare.com/rules/url-forwarding/bulk-redirects/create-dashboard/
Create Bulk Redirects in the dashboard · Cloudflare Rules docs
To create Bulk Redirects in the Cloudflare dashboard you must:
and for preview/deployment links, you can enable Access on them from Pages Project Settings, Magic Link: https://dash.cloudflare.com/?to=/:account/pages/view/:pages-project/settings
ah thanks, I was just playing around with that