1. Advantages
refer to:
CDN Tuning Guide (2) Make full use of Cloudflare
https://blog.tsinbei.com/archives/1313/
2. Access
Assumptions:
Origin IP: 8.8.8.8
Domain name resolved to the origin IP (i.e. "fallback domain"): cname.xxx.xxx
Domain name accessed by CNAME: yyy.yyy.yyy
Log in to the Cloudflare console, go to the DNS - Records page, parse a cname.xxx.xxx
record, point to the origin IP, and check "Proxy":
Go to the SSL/TLS - Custom Hostname page. If it has never been enabled, you need to activate it first:
Here is an example of selecting the payment method PayPal:
To authorize, fill in the necessary information:
Complete the activation and set the "fallback domain" to cname.xxx.xxx
:
After the rollback domain status changes to "valid", add a custom host name:
If you want to get A/A+ with SSL Labs, the minimum TLS version is TLS 1.2; I choose TLS 1.1. The verification method uses TXT verification.
Parse according to the verification information, Ignore the warning that the custom domain name does not have a CNAME to the fallback domain. After a few minutes, click "Refresh" and you will find that the status changes to "valid".
If this occurs:
The hostname is using Cloudflare and cannot be activated with an TXT or HTTP validation token. To activate the custom hostname, the DNS target needs to point to the SaaS zone.
You can refer to the articles on this site:
Troubleshooting Cloudflare's inability to verify custom hostnames using TXT
https://blog.tsinbei.com/archives/1267/
In addition, as long as the region corresponding to the CA (such as an "offshore" line using DNSPod) is resolved to Cloudflare, HTTP verification will be automatically used when the certificate is about to expire.
The access is now complete, Enjoy it!
Custom Hostnames: CNAME CDN by Cloudflare for SaaS
Comments