Recent changes to bugs

#21 DNS forwarder not working if on same machine

2018-06-29T03:31:32.464000Z

Removed this check, should work now.

#25 /tmp/opendhcp.state

2018-06-29T03:30:16.964000Z

Should have been fixed in higher versions.

#20 Primary - Secondary Replication not stable

2015-03-31T05:41:51.141000Z

These are very stable in versions 7.xx

#21 DNS forwarder not working if on same machine

2015-03-31T05:41:14.033000Z

Yes it has been deliberately prevented to stop hunting.

#24 Only 32 CHILD_ZONES entries are read from configuration file

2015-03-31T05:40:09.547000Z

Yes these are 125 now in 7.xx versions.

#25 /tmp/opendhcp.state

2015-03-31T05:35:44.966000Z

You can delete the /tmp/opendhcp.state and restart the server.

/tmp/opendhcp.state

2013-03-05T09:28:15Z

version opendhcp 1.52RC2
/tmp/opendhcp.state file exist then opendhcp server did not start

1. run opendhcp
2. using for make /tmp/opendhcp.state
3. stop opendhcp
4. start opendhcp <-- did not start

but opendhcp version 1.50 is work fine
Thanks

Only 32 CHILD_ZONES entries are read from configuration file

2013-02-12T21:47:01Z

In version 6.94 I've found out that if in the CHILD_ZONES section you have more than 32 zones defined, only the first 32 are actually read and used, the remaining ones are ignored.

I've downloaded and checked the source file and have found out that in the code reading the .ini file there are some "if" and "for" loops which are tested not again the MAX_SERVERS or MAX_RANGES defines (which both equals 125) but directly against a 32 value. This applies to CHILD_ZONES section but also to other sections where the maximum number of entries is stated at 125.

I've tried quickly replacing the instances of 32 in the .cpp file with the MAX_SERVERS define and recompiled source with MinGW and the patched executable is now reading all the zones I have configured.

The patch I've applied is quite "quick and dirty" so I might have broken something else in the code, even if so far everything seems to be working good.

Dualserver for FreeBSD

2012-11-30T14:38:00Z

Dualserver doesn't work properly in FreeBSD hosts due to divergences in the network code api
affecting network interface retrieval and message broadcast.

The patches attached to this ticket are currently applied for the v6.94 of dualserver in the FreeBSD ports,
and must be integrated in the dualserver code for the future releases.

http://files.bebik.net/patches/dualserver/patch-dualserverd.cpp
http://files.bebik.net/patches/dualserver/patch-dualserverd.h

Dualserver for FreeBSD

2012-11-30T14:20:39Z

Dualserver doesn't work properly in FreeBSD hosts due to divergences in the network code api
affecting network interface retrieval and message broadcast.

The patches attached to this ticket are currently applied for the v6.94 of dualserver in the FreeBSD ports,
and must be integrated in the dualserver code for the future releases.