On-premises Key Vault will not resolve without period in suffix-keyvault-dns value #28961
Labels
Auto-Assign
Auto assign by bot
Auto-Resolve
Auto resolve by bot
Azure CLI Team
The command of the issue is owned by Azure CLI team
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
KeyVault
az keyvault
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Describe the bug
I am using az cli 2.53.1 in the official Microsoft container. If I try to do:
Then, az cli is unable to resolve my hostname. I previously passed in via
My keyvault suffix dns. It was set to:
I could not figure out why AzCLI kept reporting that the name could not be resolved. I had to add a period in front of .vault since apparently AzCLI does not append a period.
I think AzCLI should append a period. This would make it consistent with how storage endpoint works. As far as I can tell, that does not require a period.
Related command
see above
Errors
Errno -2. Name could not be resolved.
Issue script & Debug output
Not able to provide. Airgapped.
Expected behavior
AzCLI does not require a period.
Environment Summary
azure-cli 2.53.1
core 2.53.1
telemetry 1.10
Dependencies:
msal 1.24.0b2
azure-mgmt-resource 23.1.0b2
Additional context
Using Azure Stack Hub
The text was updated successfully, but these errors were encountered: