[
https://issues.apache.org/jira/browse/NIFI-8954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DEOM Damien resolved NIFI-8954.
-------------------------------
Resolution: Fixed
The default configuration for DNS Azure should be 168.63.129.16 which is able
to resolve internal resources AND external resources correctly.
{{modified /etc/resolv.conf}}
See{{}}
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances#considerations
> InvokeHTTP should support DNS-OVER-TCP
> --------------------------------------
>
> Key: NIFI-8954
> URL: https://issues.apache.org/jira/browse/NIFI-8954
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: DEOM Damien
> Priority: Major
>
> InvokeHTTP doesn't seem to support dns over TCP.
> It fails to invoke dns that does too many redirections, like
> [https://paasaddon-digitaltwin3250.api.weu.digitaltwins.azure.net|https://paasaddon-digitaltwin3250.api.weu.digitaltwins.azure.net/]
> Error message:
> java.net.UnknownHostException:
> paasaddon-digitaltwin3250.api.weu.digitaltwins.azure.net: Temporary failure
> in name resolution
> Note that curls works fine with it.
> {{nslookup paasaddon-digitaltwin3250.api.weu.digitaltwins.azure.net.}}{{;;
> Truncated, retrying in TCP mode.}}{\{Server: 192.168.250.1}}\{{Address:
> 192.168.250.1#53}}
>
> See RFC7766: https://datatracker.ietf.org/doc/html/rfc7766
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
