Messages

Gotcha, appreciate the help and info.

I understand what you are saying. I am just ranting a bit and noting that the terminology is confusing. It is just not super clear based on the naming being "DHCP static mappings". Based on the naming, I would have assumed that setting a specific MAC to an IP address (even within an active range) would make it so that the firewall will not hand out that IP via DHCP unless it is to the MAC address you have defined for that IP address. However, it seems that is not the case and that is good to know.

Gotcha, just seems like an odd concept to me. I would have figured DHCP static mapping implies that it is a reserved IP within a DHCP scope.

Just a thought, but if a static mapping needs to be out of the DHCP range to function properly then how would you even provide "DHCP" to that host your are assigning in "DHCP static mapping" that is outside the range of an active DHCP pool? Is the recommended method typically letting devices pickup DHCP then statically mapping it to something outside the range?

I think the name DHCP static mappings is just a bit confusing because "DHCP" is in the name. If the static mapping isn't in a DHCP pool then why is DHCP even in the name?

So the point of these DHCP reservations is for outside of the active DHCP scope only? I haven't had any issue with collisions on other firewalls in the past by using reservations within an active scope. Is this an OPNsense specific issue?

Just to clarify. I am referring to DHCP Static Mappings within OPNsense.

These need to be outside of the DHCP pool range in order to not be taken by something else?

Thanks for the info!

Thanks. And what about "additional pools". If I have to configure those to avoid device I want statically assigned, will those need the custom DNS servers configured in there or will the main DHCP page be referenced?

So what happens when DHCP send out a lease to a client and then I click the button under the leases page to statically set it? Does that option just not work properly?

So regardless of static IP being in or outside of the DHCP range, the DNS settings (when left blank under the IP static assignment) should default the DNS settings within the DHCP settings for that subnet?

Gotcha. I thought problems with setting static IPs within the pool had been fixed a little while back? The static assignments I have are for the most part all within active DHCP pools (I have hundreds of static IPs across multiple VLANs). What problems would I run into with this?

But yea, my main question was are those devices that are statically assigned (within a DHCP pool range that contains custom DNS servers) going to receive the same DNS servers when the static IP assignment has a blank DNS server, or are they going to receive the interface IP as the DNS server since nothing is defined in the static IP assignment for DNS.

Hello,

I have a question regarding what DNS servers are assigned to IP addresses that are statically assigned within a DHCPv4 pool.

I have an active DHCPv4 pool on my OPNsense firewall. Within that, I have custom DNS servers defined in the main DHCP page for that VLAN/subnet that are not the interface IP (for example, using 8.8.8.8 or 1.1.1.1). When creating a static IP within this pool, do I also need to define the same custom DNS servers that are referenced on the main page of the DHCP pool? I want to make sure the statically assigned IPs within the DHCP pool do not receive the interface IP as the DNS server.

Thanks.