ADF private DNS zone overrides ARM DNS resolution causing ‘Not found’ error.
Published Apr 18 2023 04:47 PM 4,722 Views
Microsoft

##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

 

Sachin215_0-1681851013038.png

 

  1.             Get the private IP of the existing private endpoint and delete the private zone
  2.             In the overview blade (default) you’ll see a table with the DNS records
  3.             Look for the one with the name ‘adf’ with Type ‘A’ and write down the IP under ‘Value’ for the next steps.
  4.             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
  5.             Go back go ‘overview’ and delete a private zone

Sachin215_1-1681930802252.png

Sachin215_2-1681851013056.png

 

 

3.   Create a new Private DNS zone with the name ‘privatelink.adf.azure.com

      1.In the main Private DNS zones page, click on ‘add’ on the toolbar

      2.  Select the subscription and resource group and add ‘privatelink.adf.azure.com’ as the name

 

Sachin215_3-1681931103445.png

  1.  Add Virtual network links and DNS ‘A’ record     

            1.  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

 

Sachin215_5-1681931279489.png

  1.             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

Sachin215_6-1681931384758.png

 

 

 

2 Comments
Co-Authors
Version history
Last update:
‎Apr 19 2023 12:36 PM
Updated by: