GitHub user lhotari added a comment to the discussion: DNS
@sindhushreem25 > its not about the extra dot in the DNS names I agree that there must be some difference between Netty 4.1.118 (or Pulsar client) and the previous versions since you are observing a difference in behavior. Please share proper examples of what connection url you use to connect in your scenario from the other namespace. I brought up "this extra dot" and the request to share your connection url (you can sanitize it) so that we could find a workaround together. When you add the extra dot, that would prevent searching any other search domains. The reason why this extra dot is relevant, it could be a possible workaround if you connect with a fully qualified FQDN from the other namespace. By appending the extra trailing dot, no search domain would ever be added, regardless of the `ndots` setting. Adding a trailing dot only makes sense for a fully qualified DNS name, as it marks the name as absolute in the DNS system. When a domain name has fewer dots than the `ndots` value, Kubernetes will try appending search domains. The default `ndots` value in Kubernetes is usually 5, which is higher than standard Linux defaults (typically 1). If it has equal to or more dots than `ndots`, it first attempts to resolve the name as absolute before trying search domains. GitHub link: https://github.com/apache/pulsar/discussions/24030#discussioncomment-12340509 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
