[DNS/SSL] Clarify HTTPS record behavior with Universal SSL and proxied hostnames#30793
Open
ngayerie wants to merge 6 commits into
Open
[DNS/SSL] Clarify HTTPS record behavior with Universal SSL and proxied hostnames#30793ngayerie wants to merge 6 commits into
ngayerie wants to merge 6 commits into
Conversation
…d hostnames Updates documentation to explain: - Manual HTTPS records on proxied hostnames are not served (Cloudflare uses auto-generated records) - Disabling Universal SSL prevents automatic HTTPS record generation for proxied hostnames - Manual HTTPS records only work for DNS-only (grey cloud) hostnames Files updated: - dns-record-types.mdx: Added note explaining proxied vs DNS-only behavior - browser-compatibility.mdx: Strengthened language about Universal SSL requirement Addresses ESCALATION-2549
github-actions
Bot
added
product:ssl
|
This is great. Could we clarify that the entire label, i.e. all records in that zone with the same name, need to be grey? See ticket, if one or more orange names exist on the same label, we also won't serve the manually added HTTPS records when USSL is disabled. |
…TPS records Added: - Explanation that a 'label' refers to all records with the same name - Examples showing when manual HTTPS records will/won't be served - Updated browser-compatibility page to reference the detailed examples
Collaborator
Author
|
how does it look now @dklbreitling ? |
|
That's great, thank you! |
hannes-cf
reviewed
May 18, 2026
|
|
||
| <Details header="Example: Manual HTTPS records and proxy status"> | ||
|
|
||
| A label refers to all DNS records in a zone that share the same name. For Cloudflare to serve a manually-added HTTPS record, every record on that label must be DNS-only (grey cloud). |
Collaborator
There was a problem hiding this comment.
Why are we introducing this talk about "labels"? The official definition of a label is the string between the dots. So for www.example.com there would be three labels, www, example, and com.
Let's scratch all references of "label" and just use the term "name" which is anyway easier to understand.
hannes-cf
reviewed
May 18, 2026
hannes-cf
reviewed
May 18, 2026
hannes-cf
reviewed
May 18, 2026
Co-authored-by: Hannes <105781579+hannes-cf@users.noreply.github.com>
hannes-cf
reviewed
May 18, 2026
hannes-cf
reviewed
May 18, 2026
Co-authored-by: Hannes <105781579+hannes-cf@users.noreply.github.com>
Co-authored-by: Hannes <105781579+hannes-cf@users.noreply.github.com>
The term 'label' has a specific DNS meaning (string between dots). Using 'name' is clearer and avoids confusion.
ngayerie
force-pushed
the
ngayerie/ESCALATION-2549
branch
from
a9f79a8 to
bc112c7
Compare
Collaborator
Author
|
Hi @hannes-cf , |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates documentation to explain:
Files updated:
Addresses ESCALATION-2549
Summary
Clarifies documentation about when HTTPS records are served and when they are not.
Problem
Customers disable Universal SSL (for policy reasons) while using Advanced Certificates, then expect HTTPS records to be served. The current documentation was ambiguous ("could impact this behavior").
Solution
Updated two pages:
/dns/manage-dns-records/reference/dns-record-types/- Added note explaining:/ssl/reference/browser-compatibility/- Strengthened caution to clearly state Universal SSL is required for automatic HTTPS record generationTicket