You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current DNS implementation extracts the first IP address from the DNS translation.
In practice, this works most of the time, however the DNS translation can produce multiple IP addresses.
Returns a list of resolved IP addresses from the DNS component.
This helps improve the dialing attempts made by TCP and WebSocket transports.
When the transport fails to dial the first IP, it can move on to the next one until addresses are exhausted (or limit reached).
This is the code where we take into account the first address we find:
The current DNS implementation extracts the first IP address from the DNS translation.
In practice, this works most of the time, however the DNS translation can produce multiple IP addresses.
litep2p/src/transport/common/listener.rs
Lines 87 to 90 in a68b713
Returns a list of resolved IP addresses from the DNS component.
This helps improve the dialing attempts made by TCP and WebSocket transports.
When the transport fails to dial the first IP, it can move on to the next one until addresses are exhausted (or limit reached).
This is the code where we take into account the first address we find:
litep2p/src/transport/common/listener.rs
Lines 105 to 118 in a68b713
The text was updated successfully, but these errors were encountered: