dnscache-conf(8)
π dnscache-conf π
okay bestie, this is the dnscache-conf page from the System Manager's Manual, and it's literally the little setup fairy that gets your DNS cache service living its best life. let's get into it π§β¨
β¨ NAME β¨
dnscache-conf β sets up a DNS cache service. that's it, that's the vibe π
πΈ SYNOPSIS πΈ
dnscache-conf acct logacct D [ ip ]
π DESCRIPTION π
okay so first thing, heads up: this is a reference page. it's the "just the facts" girlie. if you want the tutorial version, with the hand-holding and the step-by-steps, go read the instructions for:
- workstations (http://cr.yp.to/djbdns/run-cache.html)
- home computers (http://cr.yp.to/djbdns/run-cache-home.html)
- external caches (http://cr.yp.to/djbdns/run-cache-x.html)
- or upgrading from BIND (http://cr.yp.to/djbdns/run-cache-bind-1.html)
fr fr, go look at those if you're confused. this page assumes you already know what you're doing π
dnscache-conf creates a service directory D that runs dnscache(8). the name D must start with a slash and must not contain any special characters. normally D is /etc/dnscache. periodt.
you can run the service under svscan(8) by using the update-service(8) program on Debian GNU/Linux:
update-service --add D
or, alternatively, by creating a symbolic link in the svscan(8) directory (normally /service or /etc/service), like this:
ln -s D /service
the service will start within five seconds, and will be restarted upon reboot. you can use svc(8) to control the service. she's got main character energy and she's self-healing, we love that π«Ά
dnscache-conf arranges for dnscache(8) to chroot to D/root and to run under the uid and gid of acct. the name acct must not contain any special characters. no cap.
dnscache-conf arranges for dnscache(8) to listen for UDP packets and TCP connections on port 53 of ip.
ip is optional; if it is not supplied, dnscache-conf arranges for dnscache(8) to listen on 127.0.0.1. yes bestie, localhost, the classic π
dnscache-conf creates D/root/ip/127.0.0.1 so that dnscache(8) will accept queries from 127.0.0.1.
dnscache-conf puts 128 bytes of not-particularly-secret data into D/seed and arranges for dnscache(8) to pass D/seed to dns_random_init(3). if your system has a good source of random data, you can replace D/seed with 128 bytes of data from that source. ngl, "not-particularly-secret" is sending me π
dnscache-conf creates an automatically rotated log directory in D/log/main. the logs are owned by logacct. the corresponding multilog(8) processes run under the uid and gid of logacct. the name logacct must not contain any special characters. obsessed with a girlie who keeps receipts πβ¨
π SEE ALSO π
dnscache(8)svscan(8)svc(8)multilog(8)axfrdns-conf(8)rbldns-conf(8)tinydns-conf(8)walldns-conf(8)update-service(8)
okay that's the whole page bestie, every single flag, path, and caveat, untouched, unedited, we simply do not gatekeep π
and that's a wrap on the dnscache-conf(8) page, straight outta the System Manager's Manual β mwah, go slay your DNS setup π
β¨
π¦ where this page comes from
- debian bookworm: djbdns-conf 1:1.05-15+b2 Β· LicenseRef-public-domain
- debian trixie: djbdns-conf 1:1.05-22 Β· LicenseRef-public-domain
- ubuntu jammy: djbdns-conf 1:1.05-15fakesync1 Β· LicenseRef-public-domain
- ubuntu noble: djbdns-conf 1:1.05-15ubuntu2 Β· LicenseRef-public-domain
- ubuntu questing: djbdns-conf 1:1.05-22ubuntu1
- ubuntu resolute: djbdns-conf 1:1.05-22ubuntu2 Β· LicenseRef-public-domain
- ubuntu stonking: djbdns-conf 1:1.05-23fakesync1 Β· LicenseRef-public-domain
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms