I have a custom domain associated with a front-end host in azure front door. I want to delete this domain association but getting a error which says "Please remove the DNS CNAME records and try again.". Why am I getting this error. Does this mean I need to remove CNAME record from my domain provider? If it is so, it will be problematic in CI/CD pipeline.
Attaching screenshot of the error.
I've found this issue #11231 in GitHub. Looks like they have introduced this breaking change recently. But it seems like it can be disabled by registering feature flag according to comment from the issue:
az feature register --namespace Microsoft.Network --name BypassCnameCheckForCustomDomainDeletion
But be aware that it's subscription level.
Related
I would like to add a custom domain that is managed by AWS to my Azure Static Web App. Microsoft documentation shows how to add one if the DNS is managed by Azure itself. Sadly, I cannot find anything for my use case. To be more clear, the function I'd like to use with Azure command line is shown in this picture.
I have tried az staticwebapp hostname set --name FOO --hostname BAR.com which doesn't work.
I suppose you have already configured CNAME/TXT/ALIAS record with your DNS provider.
You may use --no-wait option to not wait for validation or use --validation-method "dns-txt-token" or "cname-delegation"
I would also suggest to verify your CNAME record, as often domain field must be filled with subdomain, not regular/naked domain.
Please also check if you are using the latest version of az cli.
You may check version using command az version
https://learn.microsoft.com/en-us/cli/azure/staticwebapp/hostname?view=azure-cli-latest#az-staticwebapp-hostname-set-examples
So adding a slot name as dev, would create the url as appservice-dev.azuresites.net. How can we create dev-appservice.azurewebsites.net ?
CrashOverride, the other two posters are correct. We do not allow customers to edit the internal DNS name (.azurewebsites.net) of deployment slots.
I do also want to confirm that your best solution if needing custom DNS names for your slots would be to use a custom domain name (you'll need to add a SSL cert).
We encourage you to make a feature request here so the product group is made aware of this scenario.
I am new to azure and i am exploring it now, as first step i created a free azure account and in that i created a Resource group and an App service to that resource group.
When i try to access the Url https://azurehome.azurewebsites.net/ its giving an error 'The service is unavailable.'
any help on this ?
Please follow this document to troubleshoot:
https://learn.microsoft.com/en-us/azure/app-service/troubleshoot-http-502-http-503
By the way, this problem may be caused by the region you choose, trying to change the region may be effective. I'm using Central US and it works fine.
If it still doesn't resolve, please provide more information.
If you need support, you can click this link:
https://azure.microsoft.com/en-us/support/options/
I've setup a load balancer in my resource-group with a backend pool and inbound nat rules for http and https.
Now when i try to create an auto-scale-set through a template, i have to reference to a "loadBalancerInboundNatPool". But this is, what i can decipher from the error messages, not the same as the InboundNatRules.
How do i create/find the name of my InboundNatPool, so i can reference it from my template and create my Auto-Scale-Set correctly?
The loadBalancerInboundNatPools is in vmss, you need to add this to vmss
You can take a look at existing examples doing exactly this thing:
https://github.com/Azure/azure-quickstart-templates/tree/master/201-2-vms-loadbalancer-natrules
https://github.com/Azure/azure-quickstart-templates/tree/master/201-vmss-linux-nat
and several others in that repo. I don't really understand your question, but those templates will let you do just what your goal is
We are wanting to create a subdomain, staging.example.com, to point to a staging blade in Azure. We are following this tutorial: https://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/
When we get to step 5, ("Click Save to save the domain name configuration"), we get this error:
Failed to update SSL settings for prayrchainangular(staging): There was an error processing your request. Please try again in a few moments.
We've set up an A record and two CNAME records as follows:
A record:
staging -> [IP address]
CNAME
awverify.staging -> awverify.example-staging.azurewebsites.net
staging -> example-staging.azurewebsites.net
Any ideas why we are getting this Azure error and cannot save our domain name to the staging blade?
Try the old portal:
Select your website from the list >> Dashboard >> Custom Domain (bottom bar)
or Sign out / Sign In again.
So essentially here's what happened. We were trying to use the new beta Azure at https://portal.azure.com instead of the old portal at https://manage.windowsazure.com. This article below steered us in the right direction:
http://weblogs.asp.net/scottgu/windows-azure-staging-publishing-support-for-web-sites-monitoring-improvements-hyper-v-recovery-manager-ga-and-pci-compliance
That first CNAME above (awverify.staging) was completely unnecessary. All we needed was the second one.
What's confusing is that the staging blade is a child of the main web app, and you cannot get to this staging blade on the All Items tab in the old portal. You have to go to Web Apps, and then you see an arrow to the left of each web app that toggles its hidden children. We pretty much spent an hour+ figuring that out.