Replace VNet DNS override with CoreDNS conditional forwarding

[MXClyde]

Summary

Updates Mendix on Azure documentation to reflect the new CoreDNS-based conditional DNS forwarding feature, replacing the deprecated VNet-level DNS override approach.

Changes

Documentation Updates

1. interconnecting-networks page:

   • Removed "Option 2: Override DNS Resolution on the Mendix Virtual Network" section
   • Added new "Option 2: Configure Conditional DNS Forwarding" section with:
     • How it works (CoreDNS within Kubernetes cluster)
     • Prerequisites (network connectivity, firewall rules, DNS server config)
     • How to request (support ticket with environment names, domain suffixes, DNS server IPs)
     • Important notes (longest suffix matching)

2. Configuration overview page:

   • Removed "Override DNS configuration on the vNet hosting Mendix on Azure" from self-service section
   • Added "Configure conditional DNS forwarding for internal domain resolution" to support-ticket section

Background

VNet-level DNS override broke AKS node bootstrap on network-isolated clusters (existing nodes unaffected, but new nodes failed to join during scale/upgrade events). The new CoreDNS approach provides the same functionality without infrastructure-level risks.

Related

• MXFORAZURE-837: Removing dependence on customer-side DNS configuration

🤖 Generated with Claude Code

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ katarzyna-koltun-mx
❌ Clyde Waal

---

Clyde Waal seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[MXClyde]

@katarzyna-koltun-mx ready for immediate publication!