最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

ADF self hosted IR VM unable to resolve target external azure blob DNS - Stack Overflow

programmeradmin1浏览0评论

I am trying to copy files from a internal(on premise) SFTP server source via self hosted IR VM(hosted in Azure) into target external azure blob storage via managed private endpoint using managed vnet IR.

As per analysis, Self hosted IR is taking precedence at both source and target and couldn't resolve the target azure blob URL within self hosted VMs

We have tried below options. Both options are not working

  1. Allowed to access from all networks in target azure blob.
  2. Created custom DNS rule to point azure blob URL to ADF managed private endpoint IP address as we want our data to flow through private link.

Below is the error being faced

ErrorCode=AzureBlobFailedToCreateContainer,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Unable to create Azure Blob container. Endpoint: '/', Container Name: 'inp'.,Source=Microsoft.DataTransfer.ClientLibrary,''Type=Microsoft.WindowsAzure.Storage.StorageException,Message=The remote name could not be resolved: 'xxxxxxxx.blob.core.windows',Source=Microsoft.WindowsAzure.Storage,''Type=System.Net.WebException,Message=The remote name could not be resolved: 'xxxxxxxxx.blob.core.windows',Source=System,'

As a workaround, we have updated/etc/hosts file with public IP address of target azure blob URL inside self hosted IR VMs and the copy activity worked fine without any issues. However, as azure blob IP address is dynamic we can't go into production with this workaround solution.

Please advise if any suggestions.

发布评论

评论列表(0)

  1. 暂无评论