|
| 1 | +# Hostname Pre-Validation |
| 2 | + |
| 3 | +In typical scenarios, the recommended approach for hostname validation in Umbraco Cloud is to point your DNS directly to Umbraco Cloud. This lets the platform handle the process from start to finish. However, this might not be suitable for all environments—such as when working with production domains where zero downtime is critical. |
| 4 | + |
| 5 | +In such cases, Umbraco Cloud supports using a pre-validation method that allows you to complete hostname validation and SSL certificate issuance before switching your live DNS over. This approach ensures a seamless transition with no interruptions in service. |
| 6 | + |
| 7 | +## When to Use Hostname Pre-Validation |
| 8 | + |
| 9 | +Use pre-validation when: |
| 10 | +- You’re dealing with live or production domains that require 100% uptime. |
| 11 | +- You want to avoid the brief downtime that might occur while SSL certificates are being validated after pointing DNS to Umbraco Cloud. |
| 12 | + |
| 13 | +## How to Use Hostname Pre-Validation |
| 14 | + |
| 15 | +### 1. Enable Pre-Validation for the Hostname |
| 16 | + |
| 17 | +After adding your custom hostname in the Umbraco Cloud Portal, navigate to the Hostname Settings and toggle the Pre-Validation option to enable it. |
| 18 | + |
| 19 | +Umbraco Cloud will then provide two DNS records: |
| 20 | + |
| 21 | +- A **TXT** record used to verify domain ownership. |
| 22 | + |
| 23 | +- A **CNAME** record required for the SSL certificate issuance. |
| 24 | + |
| 25 | + |
| 26 | +### 2. Add DNS Records at Your Domain Registrar |
| 27 | + |
| 28 | +Log in to your DNS provider or domain registrar and add the records provided: |
| 29 | + |
| 30 | +- **TXT Record:** |
| 31 | + |
| 32 | + Name: _cf-custom-hostname.\<hostname\> |
| 33 | + |
| 34 | + Value: Provided by Umbraco Cloud. |
| 35 | + |
| 36 | +- **CNAME Record:** |
| 37 | + |
| 38 | + Name: _acme-challenge.\<hostname\> |
| 39 | + |
| 40 | + Value: Points to a domain under Umbraco's control (e.g., \<hostname\>.53231a669c5282f8.dcv.cloudflare.com). |
| 41 | + |
| 42 | +{% hint style="info" %} |
| 43 | +DNS propagation times can vary. It might take a few minutes to several hours for your changes to become active globally. Tools like https://www.nslookup.io/ can help verify that your records are live. |
| 44 | +{% endhint %} |
| 45 | + |
| 46 | + |
| 47 | +### 3. Check Validation Status |
| 48 | + |
| 49 | +Return to the Hostname page in Umbraco Cloud. You’ll see a Hostname Information Box showing the current status of your validation. |
| 50 | + |
| 51 | +If everything is set up correctly, the status will change to Active, and the Hostname will have been validated and the SSL certificate has been issued. |
| 52 | + |
| 53 | + |
| 54 | +### 4. Point Your DNS to Umbraco Cloud |
| 55 | + |
| 56 | +Once the certificate is issued: |
| 57 | + |
| 58 | +- Update your domain's A record or CNAME to point to the Umbraco Cloud DNS (add link). |
| 59 | + |
| 60 | +- Because the certificate is already in place, your site will be accessible securely (via HTTPS) without any downtime. |
| 61 | + |
| 62 | + |
| 63 | +### 5. Disable Pre-Validation and Clean Up DNS Records |
| 64 | + |
| 65 | +After the hostname is active and secure: |
| 66 | + |
| 67 | +- Go back to Hostname Settings and disable the pre-validation method. |
| 68 | + |
| 69 | +- Remove the TXT and CNAME records you added for pre-validation. |
| 70 | + |
| 71 | +This ensures that future certificate renewals are automatically handled by Umbraco Cloud without requiring manual DNS management. |
0 commit comments