Creating CNAME with two dots

[smcmillan]

Hello-

I need to create a CNAME with two dots but I get an invalid error when attempting to do so.
Example: say my root domain is guss.com
I need my.jobs to blablabla.com

Also need to create a CNAME for a domain outside of mine. Example:
this.record.■■■■.com > the.other.domain.com

Should I use TXT records?

thanks and hope this makes sense.

[fritex]

Possible issue “in between” could be:

Subdomain too deep

This tutorial covers a possible reason for the SSL_ERROR_NO_CYPHER_OVERLAP and ERR_SSL_VERSION_OR_CIPHER_MISMATCH errors (Firefox and Chrome respectively) when seen on a subdomain. The Cloudflare universal certificates cover example.com and *.example.com. This means that it covers any subdomain one level below the domain you signed up with. It will cover www.example.com and subdomain.example.com, as these are one level below the root domain, example.com. The certificate will not cover www.sub…

Or, maybe if using unproxied hostname record cloud (DNS-only), if so?

Below article could provide us more helpful information about setting up the CNAME just in case:
https://support.cloudflare.com/hc/en-us/articles/360020348832-Understanding-a-CNAME-Setup

Possible limitation: Plan we are using.

[sdayman]

You can create the CNAME, but as @fritex pointed out, it should be DNS Only.

[mike8]

So, when creating records, I tend to but the full FQDN without last dot in the record, similar to how I do the FQDN of the canonical. So, instead of my.jobs, I type the full my.jobs.domain.tld. CF will drop the zone in the record, but the verbosity helps ensure fewer errors, I’ve noticed.

Additionally, the edge certs CF provides by default don’t cover the 3rd level subdomain. It’ll cover jobs.domain.tld, but my.jobs.domain.tld won’t match the *.domain.tld wildcard cert. you would need to either use the advanced certificate manager for $10/m to manually define that, or upload your own cert to cover it, which requires a business level account. That said, this is not the case if it’s DNS-only, but then you would need to have an SSL cert on the origin, and it wouldn’t be protected by Cloudflare’s protections.

I hope this helps.

[smcmillan]

Many thanks! This took care of my issue. It would be nice for CloudFlare to include helpful text like this in the error code.
Thanks again.