pkg.sopackage field notes

brew / 排名 9025

使用 Homebrew 安装 hickory-dns

查看 hickory-dns 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install hickory-dns

provider-native install command

概览

软件包摘要

Rust based DNS client, server, and resolver

命令和别名

  • hickory-dns

历史

项目历史与用法

Hickory DNS is a Rust DNS stack covering client, protocol, resolver, recursor, and authoritative-server use cases. The `hickory-dns` binary is the server-facing package entry point, while the repository also publishes reusable crates for application developers.

The project is historically the continuation of Trust-DNS. Its own README and rebranding issue describe the move from Trust-DNS to Hickory DNS, including the crate renames and repository move that landed with the 0.24 release line.

项目历史

The tag history starts in 2015, when the project was still Trust-DNS and early releases focused on DNS resource records, configuration-file support, server/client pieces, and DNSSEC-related work. The architecture notes say the libraries grew from non-blocking I/O before Rust's async/await ecosystem settled.

Over time, the codebase became a multi-crate DNS suite: `hickory-proto` for message encoding and transports, `hickory-client` for query/update/notify operations, `hickory-server` for hosted zones, `hickory-resolver` for application resolution, `hickory-recursor` for recursive resolution, and `hickory-dns` as the server binary.

In October 2023, the project prepared Trust-DNS 0.23.1 as the final Trust-DNS release and Hickory DNS 0.24.0 as the branding-change release. The 0.24 commit message records the crate renames, README notices, license-name updates, logo updates, and repository reference changes.

采用历史

Hickory's adoption path is split between Rust crates and system packages. The README badges and architecture file emphasize individually published crates, while the Homebrew input record shows the server binary packaged as `hickory-dns` across brew, apk, Debian, and Nix.

The resolver crate is especially important for Rust applications because the README says it can be used in place of standard OS resolution facilities. The manual also documents server and recursive-resolver operation with DNSSEC validation, which broadens Hickory from library dependency to runnable network service.

The rebrand preserved continuity for the Trust-DNS user base while making package and crate names align around Hickory. Package maintainers care about that transition because it changed names without changing the basic role of the DNS stack.

使用方式

As a command-line package, `hickory-dns` runs a DNS server or resolver from a TOML configuration. The user manual shows recursive-resolver setup with `root.hints`, `trusted-key.key`, `config.toml`, and a `hickory-dns --config=./config.toml` invocation.

As libraries, the Hickory crates cover lower-level DNS message work, direct client operations, hosted-zone server construction, application resolver integration, and recursive resolution. The README also documents DNSSEC support and feature-gated cryptography providers for DNSSEC, DNS-over-TLS, and related protocols.

为什么软件包爱好者会关心

Hickory DNS is notable in package-manager culture because it is a serious network-service package written in Rust, not just a developer convenience CLI. It gives Unix package sets a Rust-native authoritative/recursive DNS option with a library ecosystem behind it.

The Trust-DNS-to-Hickory rename is also a packaging case study: package names, crate names, documentation URLs, and repository ownership all moved together, so downstreams had to distinguish an upstream continuation from a new unrelated DNS project.

时间线

  • 2015: Trust-DNS 0.1.0 tag appears with early resource-record work.
  • 2015: 0.3.0 adds configuration-file support.
  • 2020: 0.20.0 release line includes the resolver CLI path documented by the README.
  • 2023: Trust-DNS 0.23.1 is prepared as the final Trust-DNS release.
  • 2023: Hickory DNS 0.24.0 performs the branding and crate-name transition.
  • 2025: 0.25.0 architecture notes mark old Trust-DNS crates as removed in favor of Hickory crates.

Related projects

  • Trust-DNS is the direct predecessor and former project name.
  • The Hickory crate family includes hickory-proto, hickory-client, hickory-server, hickory-resolver, hickory-recursor, hickory-util, and the hickory-dns binary.
  • BIND-style DNS server practice is a background comparison point because Hickory also uses named-style server configuration paths such as `/etc/named.toml` in packaged examples.

来源

  • Architecture notes: https://github.com/hickory-dns/hickory-dns/blob/main/ARCHITECTURE.md
  • README: https://github.com/hickory-dns/hickory-dns#readme
  • Rebranding issue: https://github.com/hickory-dns/hickory-dns/issues/2051
  • Recursive resolver manual: https://hickory-dns.org/book/hickory/recursive_resolver.html
  • Repository tags: https://github.com/hickory-dns/hickory-dns/tags

安全态势

风险级别:blue

broad file, network, media, or database tool signal.

风险分类器

blue 风险 · 中 置信度 · tool

原因

  • broad file, network, media, or database tool signal

信号

  • text:client,server

安装行为

  • 未记录 Homebrew bottle 元数据。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
./config.toml/etc/named.toml

可执行文件

已安装的可执行文件

命令类型暴露范围备注
hickory-dns可执行文件已索引可执行文件从本地可执行文件索引发现。

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-08-03
管理器版本0.26.1
管理器更新时间
本地数据未知
上游不可用
检测到的最新版本未检测到
  • OK没有生成新鲜度警告。

安装元数据

软件包元数据

软件包键brew:hickory-dns
版本0.26.1
软件包管理器Homebrew
主页https://github.com/hickory-dns/hickory-dns
仓库https://github.com/hickory-dns/hickory-dns
Bottle未记录
服务未声明

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • Geiger risk classifier
  • Nucleus package database
  • curated configuration and credential file locations
  • curated package history
  • pkgdb category and tag curation