Does the advanced certificate manager apply to only one zone or to all zones in my account?
Does the advanced certificate manager apply to only one zone or to all zones in my account?
COne zone for pay as you go. There is an account-wide enterprise acm option
Cyea, you can't use Workers like that, they're not normal servers/origins. Is the other domain in your account/in Cloudflare?
Ryes, but i want a method to can point domains from end users to mine
CAll the certs that would have been switched over should already be switched over by this point
https://developers.cloudflare.com/ssl/reference/migration-guides/lets-encrypt-chain/
For Total TLS, you have to pick the different Cert. Authority
https://developers.cloudflare.com/ssl/reference/migration-guides/lets-encrypt-chain/
For Total TLS, you have to pick the different Cert. Authority
Cloudflare will not change Total TLS certificates automatically.
Cah ok then you want CF For SaaS/Custom Hostnames
https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/
https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/
RAh, thank you
CIt's what Pages/R2 uses for Custom Domains, for example. Lets you add customer domains, issues ssl/tls for them, etc. 100 custom hostnames included for free and then $0.10/per hostname/per month for over that
RIn pricing for CF SaaS, what is Scripts?
Cyou're looking at the wrong thing lol
Csounds like you're looking at WfP
CCF For SaaS is SSL/TLS -> Custom Hostnames
Ri bought the workers platform stuff
Rand at pricing
Ri was wondering
Rwhat are scripts
Cyou don't need that for what you wanted to do/just sending traffic to a worker from customer domains. WfP is for letting users dynamically upload workers "scripts" for running them. It's like CF Pages w/ uploading your own functions
Rah, thank you
RThe DCV needs to be placed on my domain right?
Cnah that's nothing new/just how that works, been that way forever: https://community.cloudflare.com/t/mx-record-set-is-not-showing-the-same-in-lookup/391704/2?u=chaika
My understanding is mail servers generally don't have an issue with it because they do their own recursive lookups, lots of edge cases with mail
My understanding is mail servers generally don't have an issue with it because they do their own recursive lookups, lots of edge cases with mail
Cnow I wonder which ones wouldn't work with that. Postfix and Exim both have their own internal dns resolver it looks, maybe they all just do to ensure they confirm to the mail spec and handle cases like resolving spf records with precision. Mail is fun
Cwhat do you mean "Resolves fine for non-wildcards"? It has the same behavior for non-wildcards and wildcards pointing to proxied records as far as I can see, still resolves fine for mailserver lookups: https://mxtoolbox.com/SuperTool.aspx?action=mx%3aok.mx-test.yarn.network&run=toolpage
CBusiness can do subdomains (partial zones) with CNAMEs as long as the underlying domain isn't using Cf DNS, and ENT can do partial zones with Nameserver delegation regardless of underlying DNS.
Other then that you can use CF For SaaS (SSL/TLS -> Custom Hostnames), free has 100 included, it can kind of work but is a bit hacky of a setup
Other then that you can use CF For SaaS (SSL/TLS -> Custom Hostnames), free has 100 included, it can kind of work but is a bit hacky of a setup
IAlso the rfc on wildcard mx entries specifically discourages the use of them xd
Iwhich makes a lot of sense
Cwell you have the CF For SaaS option even on free but it's hacky, can only have one origin server for all on them on free and it basically proxies the subdomain's traffic through that existing zone and it runs through your rules/etc within that zone
Ido you use a arbitrarily large number of subdomains for your mail service?
Iotherwise I would recommend adding an entry for each
I
Ithis was already declined
Ia catchall for what
I(it's not a bug)
