This project explores how to configure custom DNS settings for applications deployed across different Azure services. It showcases three deployment models, each bound to a custom domain, allowing developers and architects to understand the process of domain binding, DNS record setup, and service-specific configurations:
- https://app-service-deployment.enricogoerlitz.com/
- https://container-apps-deployment.enricogoerlitz.com/
- https://front-door-deployment.enricogoerlitz.com/
All deployments demonstrate how to use custom subdomains managed via AWS Route 53 for DNS hosting, emphasizing interoperability and cross-cloud DNS management.
$ terraform apply- Navigate to the App Service →
Custom domains - Click on "Add custom domain"
- Add a CNAME or A-Record and the required TXT record to your domain provider (Route 53 in this case):
- Validate the domain ownership and confirm the binding:
Note: DNS propagation can take up to 5 minutes.
Visit: https://app-service-deployment.enricogoerlitz.com/
$ terraform apply- Navigate to Container Apps →
Custom domains - Click on "Add custom domain"
- Add a CNAME or A-Record and the required TXT record to your domain provider:
- Validate the domain ownership and confirm the binding:
Note: DNS propagation can take up to 5 minutes.
Visit: https://container-apps-deployment.enricogoerlitz.com/
$ terraform apply- Create a new domain in the Front Door Manager:
- Click on the "Pending" status and add the TXT record provided by Azure to your DNS provider:
-
Associate the domain with the appropriate Front Door endpoint.
-
In your DNS provider, create a CNAME record:
CNAME: front-door-deployment.enricogoerlitz.com → <azure_fd_endpoint>.azurefd.net -
Confirm domain association in the Front Door manager:
Wait a few minutes for the domain binding to complete.
Visit: https://front-door-deployment.enricogoerlitz.com/
