Release Notes: This release fixes a major problem in 2.44 where the DNS function failed unless the --min-port flag was given.
Release Notes: This is a stability release. It fixes crash problems in 2.43. The crashes occurred when a DHCP client renewed a non-existent lease for an invalid subnet, when a DHCP client that does not have a lease performed a DHCPINFORM, and when the network configuration changed.
Release Notes: This release fixes a problem introduced in 2.37 which could cause dnsmasq to hang using 100% of the CPU. This only occured when at least one infinite-time DHCP lease existed, and it could take hours or days for the problem to show, depending on the load. All 2.37 users should upgrade. This release also fixes a long-standing bug which caused dnsmasq to continually repeat a query when it received a SERVFAIL code from an upstream server. This only happened when the --strict-order configuration flag was used. All installations using --strict-order should upgrade.
Release Notes: The prime reason for this release is to add a workaround for a bug in the OpenBSD-4.0 kernel. OpenBSD-4.0 is due for release very soon and no version of dnsmasq prior to 2.35 will do DHCP on OpenBSD-4.0. This release also includes performance improvements when reading very large /etc/hosts files.
Release Notes: This release contains a single bugfix for a problem introduced by the previous release. That bug would cause a crash whenever a DHCP client requested a broadcast response.
Release Notes: This release fixes problems in the 2.21 release. It builds unpatched on Linux systems with /usr/include/linux from glibc 2.2, and three or four regressions from 2.20 provoked by particular configurations have been fixed. The only new feature is support for encapsulated vendor-specific DHCP options.
Release Notes: This release fixes confusion between NODATA and NXDOMAIN replies in the DNS server. It addresses a situation where dnsmasq could return NXDOMAIN for a query of type AAAA even though queries for the same domain for A or MX records would succeed. This bug is triggered by a change in behaviour between Windows XP SP1 and SP2, and has also been seen with certain mailer configurations. Note that the bug only occured for domains that were in dnsmasq's local configuration (from /etc/hosts or DHCP). Domains that were merely cached from upstream name servers never triggered the problem.
Release Notes: A crash bug was fixed. All users are encouraged to upgrade.
Release Notes: This release fixes a brown-bag bug in version 2.1 The bug disabled all DHCP functionality on Linux systems which have IPv6 enabled in the kernel.
Release Notes: This fixes a crash/lockup bug present in versions 1.14, 1.15, and 1.16. All users of those versions who use the DHCP facilities of dnsmasq should upgrade.