[
https://issues.apache.org/jira/browse/KAFKA-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3352:
-------------------------------
Description:
We use `InetSocketAddress.getHostName` in `Cluster.bootstrap` and
`SocketServer` This call can cause a reverse DNS look-up if an IP address is
used in the configuration. `getHostString` avoids the reverse DNS look-up.
`InetAddress.getHostName` has the same issue and it's used in
`SaslChannelBuilder`, `SslChannelBuilder` and `ZookeeperConsumerConnector`. I
am not changing these because the the former two actually require the FQDN
while the latter is on its way to deprecation.
was:We use `InetSocketAddress.getHostName` in Cluster.bootstrap. This call
can cause a reverse DNS look-up if an IP address is used in the configuration.
`getHostString` avoids the reverse DNS look-up.
> Avoid DNS reverse lookups
> -------------------------
>
> Key: KAFKA-3352
> URL: https://issues.apache.org/jira/browse/KAFKA-3352
> Project: Kafka
> Issue Type: Improvement
> Reporter: Ismael Juma
> Assignee: Ismael Juma
>
> We use `InetSocketAddress.getHostName` in `Cluster.bootstrap` and
> `SocketServer` This call can cause a reverse DNS look-up if an IP address is
> used in the configuration. `getHostString` avoids the reverse DNS look-up.
> `InetAddress.getHostName` has the same issue and it's used in
> `SaslChannelBuilder`, `SslChannelBuilder` and `ZookeeperConsumerConnector`. I
> am not changing these because the the former two actually require the FQDN
> while the latter is on its way to deprecation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
