Skip to content
This repository has been archived by the owner on Nov 28, 2020. It is now read-only.

TCP connecter does not check for DNS TTL expiration #85

Open
jean-airoldie opened this issue Jun 21, 2019 · 4 comments
Open

TCP connecter does not check for DNS TTL expiration #85

jean-airoldie opened this issue Jun 21, 2019 · 4 comments
Labels
bug Something isn't working

Comments

@jean-airoldie
Copy link
Owner

See this issue for more info.

@jean-airoldie jean-airoldie added the bug Something isn't working label Jun 21, 2019
@jean-airoldie
Copy link
Owner Author

For now we should stick to using static IPs for known endpoints.

@jean-airoldie
Copy link
Owner Author

jean-airoldie commented Jun 21, 2019

This can be a major issue if a bound socket is used in a docker swarm or k8 cluster since they use their owned DNS to refer to containers.

@jean-airoldie
Copy link
Owner Author

Getting the DNS TTL in a cross platform manner is probably quite a pain, to as a temporary mitigation, a static DNS_TTL could be set.

@jean-airoldie
Copy link
Owner Author

jean-airoldie commented Jun 21, 2019

Another temporary client work around would be to call disconnect then connect on last_endpoint again after the recv_timeout period expired.
edit: This is event better than a TTL since we can detect the DNS update as soon as it occurs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant