Document self-managed Private DNS zone option for internal service resolution - #11758
Open
MXClyde wants to merge 1 commit into
Open
Document self-managed Private DNS zone option for internal service resolution#11758MXClyde wants to merge 1 commit into
MXClyde wants to merge 1 commit into
Conversation
…solution Customers hit deny-assignment errors when trying to create Private DNS zones/records directly inside the Managed Resource Group. Clarify that the zone should instead be created in a resource group the customer controls and linked to the Mendix vNet via a virtual network link.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Customers configuring outbound DNS resolution from Mendix apps to internal on-prem services were hitting Azure deny-assignment errors when trying to create a Private DNS zone (and its record sets) directly inside the Mendix on Azure Managed Resource Group. The existing docs mentioned creating/using a Private DNS zone as an option, but did not explain this restriction or where the zone should actually live.
This PR expands that section to clarify: create the Private DNS zone in a resource group you control, outside the Managed Resource Group, then link it to the Mendix vNet via a virtual network link. A cross-link is also added from the support/customization page.
Changes
content/en/docs/deployment/mx-azure/configuration/mx-azure-network-interconnecting-networks.md: expanded the "DNS Name Resolution towards Resources in Other Networks" section into two clearly labeled options, with step-by-step instructions and the deny-assignment rationale for Option 1.content/en/docs/deployment/mx-azure/mx-azure-support.md: added a cross-link bullet to the connectivity customization list.Test plan
#name-resolution-dns-override,#dns-zone-outside-mrg) resolve correctly@katarzyna-koltun-mx this can be merged immediately once approved.