Skip to content

Commit b48f56e

Browse files
committed
Apply suggestions from Mikulas
1 parent 26af578 commit b48f56e

File tree

1 file changed

+22
-6
lines changed

1 file changed

+22
-6
lines changed

umbraco-cloud/go-live/manage-hostnames/hostname-pre-validation.md

Lines changed: 22 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,22 @@
11
# Hostname Pre-Validation
22

3-
In typical scenarios, the recommended approach for hostname validation in Umbraco Cloud is to point your Domain Name System (DNS) directly to Umbraco Cloud. The platform handles the process from start to finish. However, this may not be suitable for all environments, such as when working with production domains where zero downtime is critical.
3+
When adding a hostname to Umbraco Cloud, we ask you to point your DNS records to Umbraco Cloud.
44

5+
Sometimes it's difficult to change the DNS record to point to Umbraco Cloud due to:
6+
- Existing proxy/WAF in front of the hostname (hostname is proxied outside of Umbraco Cloud)
7+
- Requiring a zero downtime migration to Umbraco Cloud (hostname needs to be ready in Umbraco Cloud before pointing DNS records to Umbraco Cloud)
8+
9+
Hostname pre-validation let's you add a hostname to Umbraco Cloud, activate the routing and generate a certificate for the hostname before pointing the hostname to Umbraco Cloud.
10+
11+
After the pre-validation completes you can either keep using an outside proxy or migrate the hostname fully to Umbraco Cloud by pointing the DNS records to Umbraco Cloud.
512

613
## When to Use Hostname Pre-Validation
714

8-
Use pre-validation when:
15+
Use pre-validation in any of the following situations:
916

1017
- You're dealing with live or production domains that require 100% uptime.
11-
- You want to avoid the brief downtime that may occur while TLS certificates are being validated after pointing DNS to Umbraco Cloud.
18+
- The hostname will be proxied in front of Umbraco Cloud
19+
- You want to avoid the brief downtime that may occur while Transport Layer Security (TLS) certificates are being validated after pointing DNS to Umbraco Cloud.
1220

1321
## How to Use Hostname Pre-Validation
1422

@@ -60,11 +68,15 @@ The status will change to Active when everything is set up correctly. The hostna
6068

6169
pre-validation-status-modal
6270

63-
### 4. Point Your DNS to Umbraco Cloud
71+
### 4. Point Your DNS to Umbraco Cloud / Activate proxying
72+
73+
Once the certificate is issued:
74+
75+
a) Update your domain's A record or CNAME to point to [Umbraco Cloud DNS] (README.md#domains)
6476

65-
Once the certificate is issued, update your domain's A record or CNAME to point to the Umbraco Cloud DNS (add link).
77+
b) Update your proxy to serve traffic from Umbraco Cloud
6678

67-
Your site will be accessible securely via HTTPS without any downtime because the certificate is already in place.
79+
Your site will be accessible securely via HTTPS without any downtime because the certificate and routing set-up is in place.
6880

6981
### 5. Disable Pre-Validation and Clean Up DNS Records
7082

@@ -75,6 +87,10 @@ After the hostname is active and secure:
7587

7688
Umbraco Cloud will automatically handle future certificate renewals without the need for manual DNS management.
7789

90+
{% hint style="info" %}
91+
In a proxy case you'll need to ensure that the URI `http://{custom-hostname}/.well-known/acme-challenge/{token}` is accessible.
92+
{% endhint %}
93+
7894
## Custom Certificate
7995

8096
If you plan to use a [custom certificate](security-certificates), the Hostname Pre-Validation method can be used to prove ownership of the hostname. This is done before binding the custom certificate.

0 commit comments

Comments
 (0)