GitHub user lhotari added a comment to the discussion: DNS
@sindhushreem25 You should use `pulsar+ssl://pulsar-proxy.op.svc.cluster.local.:6651` as the `serviceUrl` in your client to avoid this issue. That will prevent all unnecessary DNS lookups on the client side. I hope that helps. I haven't found any change on Netty side triggering this behavior. Using an absolute FQDN name will fix the issue. An absolute FQDN name is one that ends in the root domain, which is represented by the trailing dot. You can find more information about FQDN and the trailing dot [here](https://www.f5.com/glossary/fqdn#:~:text=Trailing%20dot). GitHub link: https://github.com/apache/pulsar/discussions/24030#discussioncomment-12562966 ---- This is an automatically sent email for commits@pulsar.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@pulsar.apache.org
