Welcome to Microsoft Q&A, thank you for posting your question here!
Regarding your questions, you need a best way to resolve any conflicts when attempting to setup the Azure Private DNS, to avoid conflicts in existing Private DNS zones within Azure.
To eliminate conflicts in existing Private DNS zones within Azure, you can use the following steps:
- Create a new private DNS zone.
- Move all conflicting records from the existing zone to the new zone.
- Update the virtual network links to use the new private DNS zone.
- Delete the conflicting records from the old zone.
- You can also use Azure Private Endpoint DNS configuration to resolve conflicts between virtual networks.
You can read more from the following links:
Also, about your statement: Private Endpoints does not have a method to prevent duplication.
To prevent duplication in private endpoint azure, you can use duplicate detection.
Duplicate detection helps keep track of the application-controlled MessageId of all messages sent into a queue or topic during a specified time window. If any new message is sent with MessageId that was logged during the time window, the message is reported as accepted (the send operation succeeds), but the newly sent message is ignored and dropped as a duplicate.
You can also set up duplicate detection rules to keep your data clean.
You can use the below links to read more:
Hope this is helpful.
Kindly let me know if the above helps or you need further assistance or explanation on this issue.