grpc dotnet DNS-resolving on recreating tcp connection in channel

[KirillKurdyukov]

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?

[gfoidl]

For .NET 5 and newer and when not on Blazor, then the SocketsHttpHandler is used as HTTP-message handler, thus all what you can configure there applies for gRPC too (The connection is reestablished periodically to reflect the DNS or other network changes), so you may be especially interested in PooledConnectionLifetime property.

[KirillKurdyukov]

Okey,

For .NET 5 and newer and when not on Blazor, then the SocketsHttpHandler is used as HTTP-message handler, thus all what you can configure there applies for gRPC too (The connection is reestablished periodically to reflect the DNS or other network changes), so you may be especially interested in PooledConnectionLifetime property.

Ok! So if I understand correctly: if I don't specify the PooledConnectionLifetime property, then DNS resolution will only happen when the transport becomes unavailable (for example, when an Unavailable error code). Is that correct?