Hi I fixed it by deleting the CNAME, Adding the www TXT, manually - it then validated, then I deleted the TXT and re-added the CNAME - and it worked.
But thanks for the response, it's much appreciated.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Resource:
NebulyxWebSiteResource Group: NebulyxWebSite_group
Region: West Europe
Problem description: Custom domain www.nebulyx.ai is stuck in Validating status for more than 12 hours, despite TXT and CNAME DNS records being configured correctly and visible globally.
Steps taken so far:
Added CNAME record:
Name: www
Type: CNAME
Value: `xxxxxxx.2.azurestaticapps.net`
```1. Added TXT record for validation:
Name: `asuid.www`
Type: TXT
- Value: `<Token>`
- Verified propagation globally (nslookup, whatsmydns) — records are visible across multiple regions.
Checked with Azure CLI:
```dockerfile
az staticwebapp hostname list --name NebulyxWebSite --resource-group NebulyxWebSite_group -o table
Result shows:
`nebulyx.ai` → Ready
`www.nebulyx.ai` → Validating (ValidationToken = `xxxxxxx`)
Curl to `https://www.nebulyx.ai` resolves to Azure Front Door but returns a generic error page.
```**Expected behavior:** Azure should validate the TXT record, flip domain status to **Ready**, and provision the SSL certificate.
**Actual behavior:** `www.nebulyx.ai` remains stuck in *Validating* despite DNS being correct and resolvable.
**Impact:** Unable to serve traffic over HTTPS from `www.nebulyx.ai`. Root domain (`nebulyx.ai`) is working fine.
**Request:** Please investigate and force validation for `www.nebulyx.ai` so SSL can be provisioned.**Resource:**
Static Web App Name: `NebulyxWebSite`
Resource Group: `NebulyxWebSite_xxxxx`
Region: West Europe
**Problem description:**
Custom domain `www.nebulyx.ai` is stuck in *Validating* status for more than 12 hours, despite TXT and CNAME DNS records being configured correctly and visible globally.
**Steps taken so far:**
Added CNAME record:
Name: `www`
```yaml
Type: CNAME
Value: `xxxxxxxx2.azurestaticapps.net`
Added TXT record for validation:
Name: `asuid.www`
Type: TXT
Value: `xxxxxxxxxx`
Verified propagation globally (nslookup, whatsmydns) — records are visible across multiple regions.
Checked with Azure CLI:
```
az staticwebapp hostname list --name NebulyxWebSite --resource-group NebulyxWebSite_group -o table
```
Result shows:
`nebulyx.ai` → Ready
`www.nebulyx.ai` → Validating (ValidationToken = `xxxxxxxxx`)
Curl to `https://www.nebulyx.ai` resolves to Azure Front Door but returns a generic error page.
```**Expected behavior:**
Azure should validate the TXT record, flip domain status to **Ready**, and provision the SSL certificate.
**Actual behavior:**
`www.nebulyx.ai` remains stuck in *Validating* despite DNS being correct and resolvable.
**Impact:**
Unable to serve traffic over HTTPS from `www.nebulyx.ai`. Root domain (`nebulyx.ai`) is working fine.
**Request:**
Please investigate and force validation for `www.nebulyx.ai` so SSL can be provisioned.
Edited: Masked sensitive data
Hi I fixed it by deleting the CNAME, Adding the www TXT, manually - it then validated, then I deleted the TXT and re-added the CNAME - and it worked.
But thanks for the response, it's much appreciated.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more