GitHub user lhotari edited a comment on the discussion: DNS
> when the client tries to talk to pulsar proxy pods we provide the service url > and pulsar url like https://pulsar-proxy/. pulsar:8443 this internal will > resolve to https://pulsar-proxy.pulsar.svc.cluster.local:8443/ and this > connection works and clients are able to communicate with pulsar server . @sindhushreem25 Did you try using `https://pulsar-proxy.pulsar.svc.cluster.local:8443`? If that doesn't stop additional queries, add the extra dot such as `https://pulsar-proxy.pulsar.svc.cluster.local.:8443`. Have you already tried this? You should be using the fully qualified domain name (FQDN) avoid any additional DNS lookups due to search domains. Sometimes it's necessary to add the trailing dot. This was explained in my previous message. GitHub link: https://github.com/apache/pulsar/discussions/24030#discussioncomment-12384047 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
