Add dnsResolver configuration option for randomized DNS load balancing#3577
Open
pavansai1 wants to merge 4 commits intoapple:mainfrom
Open
Add dnsResolver configuration option for randomized DNS load balancing#3577pavansai1 wants to merge 4 commits intoapple:mainfrom
pavansai1 wants to merge 4 commits intoapple:mainfrom
Conversation
Lukasa
approved these changes
Apr 17, 2026
Contributor
Lukasa
left a comment
There was a problem hiding this comment.
Very nice, thank you @pavansai1!
auto-merge was automatically disabled
May 5, 2026 04:23
Head branch was pushed to by a user without write access
This file contains hidden or 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
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.
Motivation:
When connecting to services with multiple DNS records (e.g. Kubernetes headless services), getaddrinfo returns addresses in a deterministic order, causing all connections to go to the same backend. SwiftNIO now provides a RandomizedDNSResolver that shuffles results.
Modifications:
Add a dnsResolver property to HTTPClient.Configuration with two options: .system (default, current behavior) and randomized (uses NIO's RandomizedDNSResolver to shuffle DNS results). Apply the resolver to ClientBootstrap during connection creation.
Result:
Users can opt into randomized DNS resolution by setting config.dnsResolver = .randomized, enabling load distribution across multiple backend IPs while preserving the default behavior.