Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
Add the exact hostname to Azure Portal → App Service → Settings → Custom domains and complete Validate → Add; an Azure “404 Web Site not found” means DNS is reaching Azure, but App Service does not have an active binding for that hostname.^1^
Complete the custom-domain binding
- First open the app’s default address, such as
yourapp.azurewebsites.net.- If it displays the website, the app is running; continue below.
- If it does not, resolve the Web App problem before troubleshooting the custom domain.
- In the Azure portal, open: App Services → your Web App → Settings → Custom domains → Add custom domain.
- Select All other domain services because IONOS hosts the DNS.
- Enter the precise hostname being tested:
- Root/apex:
example.com - Subdomain:
www.example.com
- Root/apex:
- Compare the values shown under Domain validation with the records in IONOS. Do not reuse values from another app or an earlier configuration.^2^ For the root domain (
example.com):
ForIONOS record Host/name Value A @The App Service IP displayed by Azure TXT asuidThe Custom Domain Verification ID displayed by Azure www.example.com—recommended configuration:
Do not configure both an A and CNAME record for the same hostname because that creates a DNS conflict.^3^IONOS record Host/name Value CNAME wwwThe app’s default hostname, such as yourapp.azurewebsites.netTXT asuid.wwwThe Custom Domain Verification ID displayed by Azure - Return to the Add custom domain dialog and select Validate.
- Both DNS checks should show green check marks.
- Select Add; validation alone does not finish the hostname mapping.
- Confirm the hostname now appears in the Custom domains list as successfully added or active.^2^
- Test both HTTP and HTTPS. If an App Service Managed Certificate was selected, certificate creation can take several minutes after the domain is added.
If validation does not succeed
Check the public DNS response rather than only the records displayed in the IONOS control panel:
nslookup example.com
nslookup -type=TXT asuid.example.com
nslookup www.example.com
nslookup -type=TXT asuid.www.example.com
The A or CNAME result must match the value shown by the Web App, and the TXT result must contain its current verification ID. DNS propagation can take up to 48 hours, depending on the previous TTL and provider.^1^
If DNS is correct but Azure still cannot add the hostname:
- Confirm the App Service plan is a paid tier; the Free tier does not support custom domains.
- Confirm the account has Owner, Contributor, or Website Contributor access.
- Check that the hostname is not attached to another App Service, Static Web App, or Front Door resource.
- Run App Service → Diagnose and solve problems → SSL and Domains → Run All Certificates & Domains Checks.^1^
References