grpc dotnet DNS-resolving on recreating tcp connection in channel
Open
Nobody has claimed this yet.
question
- Dominant language
- C#
- Stars
- 4.5k
- Forks
- 835
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 7
Description
When using Grpc.Net.Client (GrpcChannel), will the channel refresh/re-resolve the server's DNS and establish a new TCP connection if the server’s IP changes? More specifically: after a transport (network) error, does GrpcChannel perform DNS re-resolution to pick up the new IP, or will it keep using the resolved IP from the channel's initial creation?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file or test. Start by tracing GrpcChannel's connection and DNS-resolution behavior after a transport error, then document whether a changed server IP is detected or the original address is reused; the behavior should be verified with an appropriate test or existing evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100