Recent changes to feature-requests

#32 Ability To Include Additional .ini Files

Achal Dhir — Sat, 24 Aug 2013 17:59:55 -0000

Done in release 7.10

Ability To Include Additional .ini Files

Anonymous — Thu, 14 Feb 2013 04:46:49 -0000

It would be really nice if there were a way to tell the application to read additional settings from files other than DualServer.ini, perhaps a directive that could be added to the GLOBAL_OPTIONS section such as:

config_dir=path (a directlry in which all files are considered config files)

config_file=filename1 (individual config files to be read)
config_file=filename2

Practical examples would be an admin who wishes to block ad servers by maintaining a separate file that would contain only a WILD_HOSTS section or someone who wishes to maintain a separate list of internal hosts using an independent DNS_HOSTS section. As an added bonus, admins who want to use these additional config files on multiple servers, could use a single server for updates and a simple synchronization to replicate the changes to other servers.

"Authoritative" flag

Anonymous — Thu, 29 Nov 2012 15:10:12 -0000

Hey guys, great software! Thank you! A lot of the hardware I work with defaults to DHCP, so this is invaluable when testing and initially setting up.

I was wondering, I know the ISC implementation of DHCP supports setting an "Authoritative" flag, so as not to confuse clients of which is the "real" server. Admittedly, I never looked at the RFC so I don't even know if that's considered standard or not, but it would be useful to me, so I don't accidentally plug my laptop into the company network while this is running and take everybody down! :) Is this something that could be added?

Thanks!

Return different IP addresses for same name

Anonymous — Thu, 05 Jul 2012 16:24:33 -0000

Is it possible to have the following feature:
I have a device which have two NICs:
NIC1 - 192.168.42.254
NIC2 - 192.168.142.254
The device has a name : "Instrument1"
If a laptop is connected to network 1 (NIC1), I would like that when requesting "Instrument1" DNS returns "192.168.42.254"
If a second laptop is connected to network 2 (NIC2), I would like that when requesting "Instrument1" DNS returns "192.168.142.254"

Regards

Add number of active leases

Anonymous — Thu, 21 Jun 2012 03:57:42 -0000

Hi, it's a good free tool that help us a lot.
Please, can you add a number of client devices on the html page under the active lease table.
Like here:
Active Leases
Num Mac Address IP Lease Expiry Hostname (first 20 chars)
001 11:22:33:44:55:66 192.168.0.66 yyyymmdd HH:MM:SS hostname66
---------------------------------------------------------------------------------------------------------------------------------------------------
Total Active leases: 1

remove from DNS for DHCP release

Tue, 19 Jun 2012 02:04:31 -0000

If both DHCP and DNS are used, then if a host gets an address from DHCP, a host name is automatically added to the DNS.

The reverse seems not true; when a DHCP lease is released, the host name query for that host name still return success.

Please consider making the host name no longer available from the DNS, after a DHCP release occurs.

Let sname can modify

Anonymous — Fri, 15 Jun 2012 09:09:45 -0000

The Server Host Name (sname) at DHCP is directly assign the installed server name.
But, sname use for tftp server name sometimes.
I hope this item can modify by user.
Thanks.

IPV6 DNS AND DHCP

Anonymous — Fri, 04 May 2012 16:08:11 -0000

CAN YOU SUPPORT THE IPV6 ?
THANKS

support of Option 82

Anonymous — Thu, 01 Mar 2012 16:14:26 -0000

I tried to assing IP addresses based on option 82. This would give me the possibility to assign defined IP-addresses to end-devices dependend on the connection port of my network.
As I saw a specific client is always identified by his MAC-address. It would be great to have a client identified by the option 82 value,

work without physical network connection (for VMware client)

guru1968 — Tue, 14 Jun 2011 14:44:19 -0000

I have an VMware Linux with bridged networking on that NIC where Dual DHCP DNS Server is listening on, configured as DHCP client....

This does not work since Dual DHCP DNS Server is not listening on that NIC until a physical Link-Partner is connected!
-- could you please allow an only virtually bridged NIC (without anything physically connected to it) to be supported as well?