[PR #1859] [MERGED] remove named binary #2656

New issue

Closed

opened 2026-03-16 11:01:07 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 11:01:07 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hickory-dns/hickory-dns/pull/1859
Author: @HLFH
Created: 12/15/2022
Status: ✅ Merged
Merged: 12/19/2022
Merged by: @bluejekyll

Base: main ← Head: remove-named-binary

📝 Commits (3)

18f55a9 remove named binary
933e703 remove DEPRECATED comment for removed binary named
f4dd935 set target/debug/named to target/debug/trust-dns

📊 Changes

2 files changed (+1 additions, -6 deletions)

View changed files

📝 bin/Cargo.toml (+0 -5)
📝 bin/tests/server_harness/mod.rs (+1 -1)

📄 Description

The named binary is a duplicate of the trust-dns binary.
They both take the same path src/named.rs.

People may think having a named binary offers a drop-in replacement with BIND.
But at the same time, it conflicts with BIND and the named binary.
I think Trust-DNS provides enough compatibility by itself with BIND but does not need to provide as well a named binary.

Some users may have installed on their system both BIND and Trust-DNS.
They may want to use or try both for some reasons.
Or they may use BIND only for BIND utilities such as dig, host and nslookup.
On Arch Linux, BIND and the BIND utilities are part of the same package.
And overwriting the named binary would just create an unnecessary conflict.
For example, PowerDNS, another BIND alternative, does not conflict with BIND because it does not provide a named binary.
Trust-DNS is a great brand in the making, and I believe we should promote more the use of the trust-dns binary.

_{🔄 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/1859 **Author:** [@HLFH](https://github.com/HLFH) **Created:** 12/15/2022 **Status:** ✅ Merged **Merged:** 12/19/2022 **Merged by:** [@bluejekyll](https://github.com/bluejekyll) **Base:** `main` ← **Head:** `remove-named-binary` --- ### 📝 Commits (3) - [`18f55a9`](https://github.com/hickory-dns/hickory-dns/commit/18f55a98b4d8a3521b7a47d4f45d4836f93c3dda) remove named binary - [`933e703`](https://github.com/hickory-dns/hickory-dns/commit/933e703ae2f6137c35491289869da306fc34a623) remove DEPRECATED comment for removed binary named - [`f4dd935`](https://github.com/hickory-dns/hickory-dns/commit/f4dd935a2541994f84e70eeab61288d335bdea73) set target/debug/named to target/debug/trust-dns ### 📊 Changes **2 files changed** (+1 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `bin/Cargo.toml` (+0 -5) 📝 `bin/tests/server_harness/mod.rs` (+1 -1) </details> ### 📄 Description The `named` binary is a duplicate of the `trust-dns` binary. They both take the same path `src/named.rs`. People may think having a `named` binary offers a drop-in replacement with BIND. But at the same time, it conflicts with BIND and the `named` binary. I think Trust-DNS provides enough compatibility by itself with BIND but does not need to provide as well a `named` binary. Some users may have installed on their system both BIND and Trust-DNS. They may want to use or try both for some reasons. Or they may use BIND only for BIND utilities such as `dig`, `host` and `nslookup`. On Arch Linux, BIND and the BIND utilities are part of [the same package](https://archlinux.org/packages/extra/x86_64/bind/). And overwriting the `named` binary would just create an unnecessary conflict. For example, [PowerDNS](https://archlinux.org/packages/community/x86_64/powerdns/), another BIND alternative, does not conflict with BIND because it does not provide a `named` binary. Trust-DNS is a [great brand in the making](https://letsencrypt.org/2022/12/05/ed-letter-2022.html), and I believe we should promote more the use of the `trust-dns` binary. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>