[GH-ISSUE #1721] Add new algorithms to the NameserverPool for rotating nameservers used when making queries #747

New issue

Closed

opened 2026-03-16 00:07:24 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 00:07:24 +03:00

Owner

Originally created by @bluejekyll on GitHub (Jun 6, 2022).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1721

Is your feature request related to a problem? Please describe.

Some namesevers will rate-limit clients. We should come up with new algorithms and policies for how to choose the a nameserver in the pool for each next query.

Describe the solution you'd like

We should use this thread to create requirements. Today's algorithm is pretty basic. It works by reordering the Nameservers on each request, but does not currently offer any form of rate-limiting or forced rotation. Additionally it would be nice to track the latency to each nameserver and use that for prioritizing requests.

Originally created by @bluejekyll on GitHub (Jun 6, 2022). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1721 **Is your feature request related to a problem? Please describe.** Some namesevers will rate-limit clients. We should come up with new algorithms and policies for how to choose the a nameserver in the pool for each next query. **Describe the solution you'd like** We should use this thread to create requirements. Today's algorithm is pretty basic. It works by reordering the Nameservers on each request, but does not currently offer any form of rate-limiting or forced rotation. Additionally it would be nice to track the latency to each nameserver and use that for prioritizing requests.

kerem

2026-03-16 00:07:24 +03:00

closed this issue
added the
perf

ops

crate:resolver

crate:recursor
labels

kerem commented

2026-03-16 00:07:40 +03:00

Author

Owner

@djc commented on GitHub (Aug 14, 2023):

#1920 and #1784 made some progress on this, I think.

@djc commented on GitHub (Aug 14, 2023): #1920 and #1784 made some progress on this, I think.

kerem commented

2026-03-16 00:07:45 +03:00

Author

Owner

@divergentdave commented on GitHub (Nov 15, 2024):

I think PR #2522 finished up the last piece of this, by including all nameservers for a zone in pools used by the recursor. The recursor builds pools using ServerOrderingStrategy::QueryStatistics, so we are getting the latency-based prioritization.

Is there anything else we'd like to do here, or should we close this out?

@divergentdave commented on GitHub (Nov 15, 2024): I think PR #2522 finished up the last piece of this, by including all nameservers for a zone in pools used by the recursor. The recursor builds pools using `ServerOrderingStrategy::QueryStatistics`, so we are getting the latency-based prioritization. Is there anything else we'd like to do here, or should we close this out?

kerem commented

2026-03-16 00:07:51 +03:00

Author

Owner

@djc commented on GitHub (Nov 15, 2024):

Let's close it.

@djc commented on GitHub (Nov 15, 2024): Let's close it.

kerem referenced this issue

2026-03-16 02:17:52 +03:00

[PR #747] [MERGED] use serde derive feature instead of serde_derive #1647