Bug 275803 - dns/djbdns: restore port
Summary: dns/djbdns: restore port
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Robert Clausecker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-17 12:54 UTC by Robert Clausecker
Modified: 2024-12-02 09:15 UTC (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Clausecker freebsd_committer freebsd_triage 2023-12-17 12:54:45 UTC
By request of diizzy@, this new PR tracks the effort to restore dns/djbdns.

I'm planning to work on this but have not currently found sufficient time to do so.
Comment 1 Fernando Apesteguía freebsd_committer freebsd_triage 2023-12-17 17:55:02 UTC
^Triage: reporter is committer, assign accordingly.
Comment 2 mij@sshguard.net 2024-02-29 12:17:56 UTC
Upvoting this too.

Enough people voiced disappointment in the ticket tracking the removal of this port from the tree @ bug #256450 .

djbdns is still widely used. The fact it had no changes for a long time was a design goal since its beginning -- and why many people still appreciate running it.

For the same reason, there's no reason to take the port off the tree. It requires no maintenance and we don't need to save 2KB.

The argument to dissuade people from using "unmaintained software" is bogus. We are adults, if you don't want to use it, you're welcome -- but leave the rest of us alone.

@Robert I appreciate your intention.
Comment 3 cweimann 2024-03-06 20:30:19 UTC
Yes, please put it back!!!   I've been using it for the 20 years it has been 'unmaintained' and everytime there is a major dns catastrophe or hack I am immune.
Comment 4 Matt Simerson 2024-03-14 00:08:28 UTC
Thanks for any effort to resurrect. I'm another long time user. I've had djbdns deployed in production (along with Knot & NSD & BIND for decades. Unmaintained is not the same as non-useful.
Comment 5 Robert Clausecker freebsd_committer freebsd_triage 2024-03-14 09:30:53 UTC
Does one of you know of a maintained patch set for the port?

If not, I'll have to try and play puzzle with the patches floating around.
Comment 6 Matt Simerson 2024-03-15 07:40:08 UTC
The IPv6 patch is the only one I care about and it's still on fefe's site and applies cleanly. I have a djbdns install script that does all I need. I keep a couple tinydns server instances in my pool. I expect that others that have also provided continuously available DNS service with no downtime since 1996 also believe in network diversity and genetic diversity among the servers.

cd /usr/src
if [ -d djbdns-1.05 ]; then rm -r djbdns-1.05; fi
fetch -m http://cr.yp.to/djbdns/djbdns-1.05.tar.gz
fetch -m http://www.fefe.de/dns/djbdns-1.05-test32.diff.xz
tar -xzf djbdns-1.05.tar.gz
cd djbdns-1.05
xzcat ../djbdns-1.05-test32.diff.xz | patch
echo cc > conf-cc
echo 'cc -s' > conf-ld
sed -i .bak -e 's/"\/"/auto_home/; s/02755/0755/g' hier.c
fetch -q -o - https://www.internic.net/domain/named.root \
    | grep ' A ' \
    | awk '{ print $4 }' \
    > dnsroots.global
make setup check
Comment 7 Slawomir Wojciech Wojtczak 2024-10-18 00:33:39 UTC
+1 from my side - its a valuable port