Which gRPC language are you using? Is it C++? If yes, this could be an issue with the "ares" DNS used by default. I suggest reproducing the issue with some logs and logging it at github.
On Sunday, September 12, 2021 at 11:37:05 PM UTC-7 sureshb...@gmail.com wrote: > In our intranet, GRPC servers are running in different computers. While > many of the servers are connecting without any issue, there are some > servers failed with error *"DNS resolution failed for service : > <hostname>:<port>"* > > The issue can be resolved by adding the environment variable > *GRPC_DNS_RESOLVER* with value *native.* > > *Questions: * > > 1. Since all the servers are running in the same network*, *what could > be the reason behind DNS resolution failure for some servers only? > 2. Is adding the *GRPC_DNS_RESOLVER degrades* name resolution > performance or any other side effect. > > We need to take a decision whether this environment variable is to be > added as part of our product installation or not to avoid any similar > issues in customer environment. > > Please let know if any other input like log files required for this issue > analysis > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/fca7dd0c-f142-43a4-80ed-8be53bb6cae9n%40googlegroups.com.
