I've thought about this as well....and would love to use native OpenBSD tools for the job.
Just a design idea: 1. Use dhcpd(8) synchronization (https://man.openbsd.org/dhcpd.8#SYNCHRONISATION) to send details of dhcp leases to a DNS creator/listener. 2. The dns creator/listener creates/updates the zone file, and 3. Send a SIGHUP to nsd(8) (https://man.openbsd.org/nsd.8#SIGHUP) to reload the zone details. Issues to consider: 1. hostname collisions - what happens (what should happen?) when more than one dhcp client has the same hostname? 2. what should ttl on these A records be? probably something much less than the dhcp lease duration (depending on how aggressive clients are at renewing soon-to-be-expired leases). I'm sure there are a thousand other things to consider here...thoughts/ideas? On Sat, Apr 25, 2020 at 3:10 PM Raymond, David <david.raym...@nmt.edu> wrote: > > I use dnsmasq (an openbsd package) on the gateway for my lab ethernet > network and it works great with minimal configuration as a local DNS > server. At home I have a Synology wireless router which does the same > as long as you tell it to make DNS reservations. Your mileage may > vary with cheaper routers. One could in principle use dnsmasq even in > this case, but I haven't tried it. > > > Dave Raymond > > On 4/25/20, bofh <goodb...@gmail.com> wrote: > > Hi, > > I searched through the archives and saw a couple of discussions about using > > Dnsmasq from a long time ago. > > > > Is that the best way to let the stuff in my home to have valid dns entries > > in my home network? > > > > How difficult is it to get the OpenBSD provided dhcpd and unbound to do > > this? > > > > Thanks. > > > > > -- > David J. Raymond > david.raym...@nmt.edu > http://physics.nmt.edu/~raymond >
