DNSmasq IP reservations are tricky for Docker hosts
A home server setup is moving older back onto a newer server running on OPNsense. The problem is that some Unraid-based containers do not show normal hostnames or es. With the older ISC DHCP setup, an IP address and a description were enough to make a reservation.
That kept the IP out of the automatic assignment range so another device would not receive it. The practical need is to reserve or exclude specific in modern DNSmasq even when the Docker-related host does not provide the usual identifying details.
Key points
- The setup uses OPNsense with a server.
- Some Unraid containers lack normal hostnames or es.
- The older ISC DHCP setup allowed a reservation with only an IP address and description.
- The goal is to keep selected out of the automatic DHCP pool.
- owners running containers should decide early how fixed internal addresses will be managed.