Skip to content

Updated wording to universal ssl cname #1813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kodster28 merged 1 commit into from
Jul 19, 2021
Merged

Updated wording to universal ssl cname #1813

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions products/ssl/src/content/edge-certificates/universal-ssl/enable-universal-ssl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ For an authoritative or full domain — domains that changed their [domain names

## Non-authoritative (Partial) domains

For non-authoritative or partial domains (domains on a CNAME setup), Universal SSL will be deployed once:
- Your domain is [activated on a CNAME setup](https://support.cloudflare.com/hc/articles/360020348832#h_988416113241544055182247).
- You have added [Domain Control Validation (DCV)](../changing-dcv-method) records to your authoritative DNS.
For non-authoritative or partial domains (domains on a CNAME setup), Universal SSL will be:
- Provisioned once the DNS record is [proxied through Cloudflare](https://support.cloudflare.com/hc/articles/360020348832#h_836723523521544131668686) (orange-clouded).
- Validated:
- Immediately if you add [Domain Control Validation (DCV)](../changing-dcv-method) records to your authoritative DNS.
- After a brief period of downtime if you **do not** add DCV records (once your traffic is proxied).