hitdns
| Crates.io | hitdns |
| lib.rs | hitdns |
| version | |
| source | src |
| created_at | 2024-01-23 12:01:56.591489 |
| updated_at | 2024-11-06 00:29:53.541016 |
| description | hitdns is a DNS forward server optimized for cache hit ratio and query latency. |
| homepage | |
| repository | https://github.com/delta4chat/hitdns |
| max_upload_size | |
| id | 1110748 |
| Cargo.toml error: | TOML parse error at line 21, column 1 | 21 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
Delta 4 (delta4chat)
documentation
README
Hit DNS - Probably the world's fastest DNS forwarder
hitdns has low query latency and a high cache hit rate. This is because it will return the last available DNS resolution result whenever possible (regardless of whether its TTL has expired) and if it does expired, it will start an update task in the background, instead of "waiting for the upstream DNS recursor to return the latest result" like other DNS resolvers (e.g. dnsmasq).
So hitdns users will only experience delays the first time they query a domain they've never queried before, and every time they query this domain after that, they'll get near-instantaneous response latency.