You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2020/08/24 14:28:00 UTC

[jira] [Resolved] (NIFI-7758) Site-to-Site and ListenTCP unnecessarily perform Reverse DNS Lookup

     [ https://issues.apache.org/jira/browse/NIFI-7758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard resolved NIFI-7758.
----------------------------------
    Fix Version/s: 1.13.0
       Resolution: Fixed

> Site-to-Site and ListenTCP unnecessarily perform Reverse DNS Lookup
> -------------------------------------------------------------------
>
>                 Key: NIFI-7758
>                 URL: https://issues.apache.org/jira/browse/NIFI-7758
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework, Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.13.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The SSLSocketChannel class in nifi-security-utils obtains the remote address's hostname via a call to InetAddress.getHostName():
> {code}
> final Socket socket = socketChannel.socket();
> this.hostname = socket.getInetAddress().getHostName();
> {code}
> This hostname is captured only for use in the message of Exceptions or logging and not programmatically. The use of this reverse DNS lookup, though, can be expensive and cause long delays in an environment where reverse DNS lookups are not available. As a result, we should use InetAddress.toString() instead, which will provide the hostname, if it is available, and the IP address without performing a reverse DNS lookup.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)