DNS failover handling #638
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
midnight-wonderer
force-pushed
the
feature/dns-failover-retry
branch
from
e63631d
to
e150bbc
Compare
|
Thank you! |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello there,
I want to add DNS failover support for the client.
This implementation inclined with Nginx's behavior when used as a reverse proxy.
I need help adding the required specs; if someone wants to help, please send a pull request to my branch.
For some context, some services use A records with multiple IP addresses, unless you are large enough to handles failover at the BGP level, this is the only practical way to eliminate a single point of failure.
But the failover technique needs client support, hence the pull request.