Dhcp
Some time ago, I set up Redundant DHCP server and DNS Resolver using OpenBSD . Time has past and one of the Raspberry Pi board I own is now running FreeBSD while the ODROID HC4 is running OpenBSD .
I secured both my DHCP server and DNS resolver services running on those boards so that I can perform maintenance on one machine without turning down the whole services set.Continue reading...
One of my OpenBSD server provides DHCP and DNS resolving for my home LAN. But it sometimes has to go into maintenance mode. And if an IoT or phone requires an IP address or an FQDN at the precise moment, I hear screaming throughout the whole house.
So I decided to have fully redundant network services using two OpenBSD servers.Continue reading...
I am migrating a bunch of services from my Synology to OpenBSD ; DHCP Server being one of them. I have configured quite a few DHCP reservations over time. And I would like a better way to migrate them to dhcpd(8) than copy & paste ; or rewrite from scratch.Continue reading...
By default, a DHCP client gets an IP address, a network gateway and a DNS server. That’s fine most of the time. But if you own an OpenBSD cloud instance that has to use DHCP to get online, you might not be satisfied with the domain-name-servers option provided by your DHCP server. Hopefully, OpenBSD provides an easy way to force your DNS:
# vi /etc/dhclient.conf (...) prepend domain-name-servers 127.0.0.1; Since then, OpenBSD will use our DNS resolver. Which is… unbound(8)Continue reading...
Switching from DHCP to static IP on a Debian system requires only a few steps:Continue reading...