Hello @Anonymous ,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
If you're using a private endpoint in a hub-and-spoke model from a different subscription or even within the same subscription, it is recommended to link the same private DNS zones to all spokes and hub virtual networks that contain clients that need DNS resolution from the zones.
A single private DNS zone is required for this configuration. Creating multiple zones with the same name for different virtual networks would need manual operations to merge the DNS records.
This is a known limitation and can be found documented in the below article:
https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns#virtual-network-workloads-without-custom-dns-server
However, we will note your feature request and will forward this to the Product team for future improvements.
Kindly let us know if the above helps or you need further assistance on this issue.
----------------------------------------------------------------------------------------------------------------
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.