ADF private DNS zone overrides ARM DNS resolution causing ‘Not found’ error.

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Community Hub.

##Steps to Migrate:

1.             Navigate to existing Private DNS zone privatelink.adf.azure.com
2.             Go to portal.azure.com
3.             Type ‘private DNS zones’ on the search bar and click on the option
4.             Click on the privatelink.adf.azure.com private zone

2.             Get the private IP of the existing private endpoint and delete the private zone
3.             In the overview blade (default) you’ll see a table with the DNS records
4.             Look for the one with the name ‘adf’ with Type ‘A’ and write down the IP under ‘Value’ for the next steps.
5.             Click on ‘Virtual network links on the left panel, write down all the Virtual Networks for the next steps and then delete all the virtual network links
6.             Go back go ‘overview’ and delete a private zone

3.             Create a new Private DNS zone with the name ‘privatelink.adf.azure.com’
4.             In the main Private DNS zones page, click on ‘add’ on the toolbar
5.             Select the subscription and resource group and add ‘privatelink.adf.azure.com’ as the name

4.             Add Virtual network links and DNS ‘A’ record
5.             In the privatelink.adf.azure.com private zone click on ‘Virtual network links’ on the left panel and then add a network link for each of the virtual networks from step 2c

5.             Add DNS ‘A’ record

•              Go back to the overview panel and click on ‘+ Record set’, type ‘adf’ as the name, TTL: 10, TTL unit: seconds, and type the IP form step 2b