Michael Tremer

IPFire 2.15 - Core Update 80 is available for testing
by Michael Tremer, July 15, 2014

This is an invitation to take part in testing IPFire 2.15 – Core Update 80. It comes with lots of new features, some bugfixes and some minor security fixes.


There has been a crowdfunding on the IPFire wishlist which raised money for implementing a DNSSEC validating DNS proxy. The DNS proxy service that is running inside of IPFire has been forked and some features that were dropped in the upstream version have been backported.

IPFire now validates every DNS response of zones that are signed. If the DNSSEC signatures do not validate a DNS error is raised and therefore spoofing attacks are not longer possible. However, it is not sufficient for the internal DNS proxy to have DNSSEC enabled. Client systems should validate DNSSEC records, too, but we think that these changes block most spoofing attacks from the Internet and only DNS spoofing attacks from the local network are possible. The cache pool size has been increased so that dnsmasq is able to cache many DNS keys and signatures and that the verification does not harm the user experience.

It is required that the DNS servers from the Internet service providers validate DNSSEC as well. If not, you may change to one of those public DNS servers in this list. There is more information about DNS and IPFire on our wiki.

The web user interface has been extended to show the status of the upstream DNS servers. Therefore it is easy to determine if the DNS servers are validating and if the IPFire DNS proxy is validating, too.

New dynamic DNS updater

A new tool to update dynamic DNS records has been written. It replaces the old, faulty and hard to maintain perl script setddns.pl. The new client is written in Python and portable to other distributions as well. It is easily extensible and avoids duplicating code. The sources can be found on our own git server or on GitHub and we are happy to receive improvements and patches that add support for new providers.

The user interface has been simplified and obsolete and deprecated features like wildcard support have been dropped.

There is support for all DNS providers that have been formerly supported. Providers that don’t exist any more have been removed and some new ones have been added: all-inkl.com, dhs.org, dns.lightningwirelabs.com, dnspark.com, dtdns.com, dyndns.org, dynu.com, easydns.com, enom.com, freedns.afraid.org, namecheap.com, no-ip.com, nsupdate.info, ovh.com, regfish.com, selfhost.de, spdns.org, strato.com, twodns.de, udmedia.de, variomedia.de, zoneedit.com

entrydns.net and opendns.com are supported, too.



New arrivals


Posted: July 15, 2014 • 933 views