←back to thread

My Own DNS Server at Home – Part 1: IPv4

(jan.wildeboer.net)
220 points speckx | 3 comments | 05 Sep 25 19:08 UTC | HN request time: 0s | source
Show context
Arch-TK ◴[05 Sep 25 21:18 UTC] No.45143732[source]▶
At home I have an openbsd box as my network gateway running unbound and nsd. Unbound handles the caching and recursion, nsd handles the local name resolution.

I have a small utility (made up of two shell scripts and a python script) which watches /var/db/dhcpd.leases for changes and parses it to produce the zonefiles for nsd.

Edit: https://paste.rs/vgr7t.txt

replies(1): >>45144273 #
1. ninkendo ◴[05 Sep 25 22:13 UTC] No.45144273[source]▶
Y’know the script approach sounds like a good idea.

I also have an OpenBSD box similar to what you describe, but I run ISC dhcpd and BIND because it’s the only setup that does old-school dynamic DNS where the dhcp server sends zone updates to BIND when a lease happens.

But I hate BIND, and not to mention this setup doesn’t work with DHCPv6 (no idea why, it should in principal…) maybe I should just do the “script to read the leases and generate the zone file” approach instead.

replies(2): >>45144654 #>>45144659 #
2. JdeBP ◴[05 Sep 25 22:55 UTC] No.45144654[source]▶
The world has been waiting for a DHCP and content DNS server that simply share a common database back-end, meaning no notifications/updates/scripts, for decades. See https://news.ycombinator.com/item?id=44395279 for more.
3. Arch-TK ◴[05 Sep 25 22:55 UTC] No.45144659[source]▶
Depends on bash, inotify-tools, ldns-utils, python

https://paste.rs/vgr7t.txt

Enjoy