Feature Requests

It seems that static dhcp leases don't get registered in the dns system.

I'd love to see this feature added too ... since it seems that linux-based firewalls do the same thing.  It would be great to not have to edit the host names manually in order to override the DNS forwarder.

[The integrated DHCP server supports static and dynamic DHCP leases]

The underlying "issue" seems to possibly be with dnsmasq itself or how it's being configured in monowall.

I quote "issue" as I tend to get an argument from some folks in that they think this isn't an issue and is how it's supposed to work (which I disagree with).


http://www.thekelleys.org.uk/dnsmasq/doc.html

The integrated DHCP server supports static and dynamic DHCP leases and multiple networks and IP ranges. It works across BOOTP relays and supports DHCP options including RFC3397 DNS search lists. Machines which are configured by DHCP have their names automatically included in the DNS and the names can specified by each machine or centrally by associating a name with a MAC address in the dnsmasq config file.

The quick but manual hack around this is to put the static IP addresses in the monowall host table.

Having monowall edit/update the local host table when static leases are added/edited/deleted would be another hack as well.

Making sure an up to date dnsmasq is being used and getting configured correctly by monowall for static dhcp leases+dns seems to be what's ultimatly needed.

Well this may explain why my nslookup attempts fail when I query a machine that's assigned a static DHCP address. 

It appears that the static DHCP assignments to not show up as active leases on the diagnostics screen either.  Maybe I'm not patient enough to see them or maybe there is some other reason for this? 

In any event there are a lot of reasons to use static DHCP, for example preserving the ability to manage IP addresses in one place while not breaking NAT assignments.  However, there are also applications, like backuppc for linux, that need nslookup to return a name. 

The best workaround I can find is to create a list of DNS overrides that match the static DHCP assignment list using the DNS forwarder domain override feature.  Of course that duplicates the same information in two places and invites problems since any changes must be done in two places to keep everything working. 

My opinion is that the logical thing would be to have static DHCP assignments picked up by DNS forwarder. 

Max L.