-
Notifications
You must be signed in to change notification settings - Fork 21k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish DNS #14425
Comments
@linusjody Thanks for the feedback! We are currently investigating and will update you shortly. |
+1 on this. We have virtual IP in overview tab, what do we pont our various custom hostnames to? |
Would be great with an update of this documentation IP is quite safe to use as it's static though the lifetime of the subscription, with a few exceptions. https://docs.microsoft.com/en-us/azure/api-management/api-management-faq#is-the-api-management-gateway-ip-address-constant-can-i-use-it-in-firewall-rules |
We have used CNAME records resolving to the Azure assigned endpoint names, e.g. proxy.azure-api.net, which allows us to have a custom domain for both the proxy and portal A records. The static IP option only allows for proxy access as far as I can tell. |
Any feedback on the steps for custom domain. Do we use CNAME's to map to the default names? |
So will just a CNAME work? |
Hi Dan, A CNAME works perfectly. I’m surprised that the documentation still hasn’t been updated to reflect this after 10 months, Thanks Nathan |
I created a pull request just now to add this to documentation |
Hi, it's unclear how we publish this publicly. Is there a CNAME or IP that we can use?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: