Dual-homed private endpoints
We use private endpoints in our backend systems, and because it is cloud, our developers/engineers need access via the frontend network! So our backend services need to be dual homed to allow connection to the DB privately! To get this to work, we are asked to implement an unmanageable workaround, because of DNS issues that were raised in ticket 120042825000729.
If we put two IP addresses under the same DNS entry, the first IP address is picked up all the time! The only solution appears that we have two different zones (with the same name), and connect each zone to a different Virtual Networok... which means our DNS team and network team end up with 10s of DNS zones with identical names, which is completely unmanagable.
Can you please look into implementing different dns entries for the same service so we can specify which IP should be used from where? We can't have the DNS deciding which IP address to return, this is causing connection issues. I.e. I want my SQL server to have multiple configurable DNS entries per private endpoint using private DNS zones.