[PR #1611] [MERGED] Add resolver.clear_cache() sync and async #2456

New issue

Closed

opened 2026-03-16 08:54:55 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 08:54:55 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hickory-dns/hickory-dns/pull/1611
Author: @dns2utf8
Created: 1/4/2022
Status: ✅ Merged
Merged: 1/4/2022
Merged by: @bluejekyll

Base: main ← Head: client_clear_cache

📝 Commits (2)

b66ad9a Add resolver.clear_cache() sync and async
a5d9593 Synchronise the docs

📊 Changes

4 files changed (+21 additions, -0 deletions)

View changed files

📝 crates/resolver/src/async_resolver.rs (+5 -0)
📝 crates/resolver/src/caching_client.rs (+5 -0)
📝 crates/resolver/src/dns_lru.rs (+4 -0)
📝 crates/resolver/src/resolver.rs (+7 -0)

📄 Description

Hi all

This is the first PR to address the network change issue #1608

I am currently not sure what is smarter:
a. dropping the resolver in the consuming application on a network change or
b. reloading the settings in this crate

Cheers,
Stefan

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hickory-dns/hickory-dns/pull/1611 **Author:** [@dns2utf8](https://github.com/dns2utf8) **Created:** 1/4/2022 **Status:** ✅ Merged **Merged:** 1/4/2022 **Merged by:** [@bluejekyll](https://github.com/bluejekyll) **Base:** `main` ← **Head:** `client_clear_cache` --- ### 📝 Commits (2) - [`b66ad9a`](https://github.com/hickory-dns/hickory-dns/commit/b66ad9a462e4eeca3aa0717abf305fecac302e9b) Add resolver.clear_cache() sync and async - [`a5d9593`](https://github.com/hickory-dns/hickory-dns/commit/a5d9593eda6a0a38c3172f520303fec2bde77c25) Synchronise the docs ### 📊 Changes **4 files changed** (+21 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `crates/resolver/src/async_resolver.rs` (+5 -0) 📝 `crates/resolver/src/caching_client.rs` (+5 -0) 📝 `crates/resolver/src/dns_lru.rs` (+4 -0) 📝 `crates/resolver/src/resolver.rs` (+7 -0) </details> ### 📄 Description Hi all This is the first PR to address the network change issue #1608 I am currently not sure what is smarter: a. dropping the resolver in the consuming application on a network change or b. reloading the settings in this crate Cheers, Stefan --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>