Maintenance Blog

We have a candidate for the upcoming 1.07 release of Net::DNS.

This release contains bugfixes and general maintenance work only.
For a complete overview see the Changes file.

Please review this candidate carefully. If no issues arise, the actual release will follow Thurday the 29th of December 2016.

Regression test results: https://www.net-dns.org/regression

Dear all,

We have just released version 1.03 of Net::DNS::SEC.

This release has no core code changes whatsoever. It contains only an altered Makefile.PL that avoids problems with old MakeMaker and improved unit tests to get 100% coverage! and to address issues arising from incompatible versions of prerequisite.

For a complete list of changes and bugfixes see the CHANGES file.

We have a new release, version 1.06 of Net::DNS.

– Parsing of scoped IPv6 has been fixed when IO::Socket::IP is used (regression since 1.05).
– Interfering middle boxes will no longer be able to hang recursive lookups and interfere with unit tests.
– Linking of CNAMEs to its target address records with resolver->nameservers() will be done case insensitive.

This release also includes updated error reporting resulting from discussion and comments from the mailing list:

• axfr() in list context returns the complete zone if successful. If an error occurs, an empty list is returned with errorstring() indicating the reason.
• axfr() in scalar context returns an iterator if successful. If a connection failure occurs, undef is returned with errorstring() indicating the reason. The iterator will raise an exception if the transfer can not be completed.
• Resolver documentation has been clarified to make explicit that errorstring() is valid immediately after an error and meaningless otherwise.

For a complete list of changes and bugfixes see the CHANGES file.

Regression testing results: https://www.net-dns.org/regression/.

We have a second candidate for the upcoming 1.06 bugfix release of Net::DNS. A list of bugfixes can be found in Changes.

This release candidate includes changes resulting from discussion and comments from the mailing list on error handling with zone transfers. Resulting in:

• axfr() in list context returns the complete zone if successful. If an error occurs, an empty list is returned with errorstring() indicating the reason.
• axfr() in scalar context returns an iterator if successful. If a connection failure occurs, undef is returned with errorstring() indicating the reason. The iterator will raise an exception if the transfer can not be completed.
• Resolver documentation has been clarified to make explicit that errorstring() is valid immediately after an error and meaningless otherwise.

In the process of reducing code complexity and improving code coverage of the unit tests, the value of errorstring() is with this release candidate *meaningless* when not consulted directly after failure, similar to the predefined perl variable $! (see perlvar). Testing successful zone transfer by testing errorstring() for a value that it was known to have before the transfer, will no longer work.

Please review this candidate carefully. In particular with respect to error handling. If now issues arise, the actual release will follow Friday the 27th of May.

Regression testing results: https://www.net-dns.org/regression/.

We have a candidate for the upcoming 1.06 bugfix release of Net::DNS.

– Parsing of scoped IPv6 has been fixed when IO::Socket::IP is used (regression since 1.05).
– Interfering middle boxes will no longer be able to hang recursive lookups and interfere with unit tests.
– errorstring() results for non-errors has been restored (“regression” since 1.05)

Besides these bugfixes, this release
– has better TSIG error reporting
– has better Resolver.pm documentation
– and has great coverage results!

If no issues arise, the actual release will follow Monday the 25th of April 2016.

We have a new release, version 1.05 of Net::DNS.

This release deals with a few ticket from request tracker.

– TSIG algorithm names will be compared case insensitive again (bug since 1.02).
– Makefile.PL will issue a warning when an earlier version of Net::DNS (before 1.01) was installed on a different (architecture dependent) location.
– The asynchronous support functions (bgsend / bgread) now support transparent retry over TCP with truncated UDP packets.

Also support for the SMIMEA resource record was added.

For a complete list of changes and bugfixes see the CHANGES file.

We have a candidate for the upcoming 1.05 bugfix release of Net::DNS.

– TSIG algorithm names will be compared case insensitive again (bug since 1.02).
– Makefile.PL will issue a warning when an earlier version of Net::DNS (before 1.01) was installed on a different (architecture dependent) location.
– The asynchronous support functions (bgsend / bgread) now support transparent retry over TCP with truncated UDP packets.

Also support for the SMIMEA resource record was added.

For a complete list of changes and bugfixes see the CHANGES file.

If no issues arise, the actual release will follow Monday the 7th of March 2016.

We have a new release, version 1.04 of Net::DNS.

This is a emergency recovery and bugfix release.

The 1.03 release of Net::DNS addressed some longstanding request tracker issues (TCP and persistent sockets for bg(send|read|isreead)), but unfortunately in such a way that dependent modules broke.

This release has fixes to make those dependent modules work again without losing the aforementioned work.

To support us in this effort we have started to do regression testing of dependent modules ourselves, by running the dependent module’s test suite against a new Net::DNS. The results of these tests are put online here: https://www.net-dns.org/regression/.

For a complete list of changes and bugfixes see the CHANGES file.

We have a candidate for the upcoming 1.04 emergency recovery and bugfix release of Net::DNS.

The 1.03 release of Net::DNS had bugfixes (TCP and persistent sockets for bg(send|read|isreead)) that were unfortunately tackled in such a way that dependent modules broke. This is something we do not want to happen.

We have been doing release candidates to help to prevent these situations from happening. We realize however that just one week is a short period to do a proper review and also that some issues might not be immediately obvious.

To improve we will from now on always do regressions testing of modules dependent on Net::DNS ourselves before doing the release candidates. The results of these regressions tests are put online here: https://www.net-dns.org/regression/. Packages that still have regression with the release candidate there do have it for known, non hazardous, or reasons that are being addressed (see footnote 1).

For a complete list of changes and bugfixes see the CHANGES file.

Because of the severity of the fixed bugs and also in an attempt to prevent further fixes based on version 1.03, this is a fast-track release candidate. We still ask you review this candidate carefully and thoroughly and report back if there are issues! If no issues arise, the actual release will follow Tuesday the 8th of December 2015.

Footnote (1)
Explanation of regressions that still occur for 1.03_03 as seen on https://www.net-dns.org/regression/:
– Mail-SpamAssassin is because of a warning given for the developer release version number and is harmless
– IO-Lambda 1.25 simply has to rollback it’s change that it did for the 1.03 release (IO-Lambda 1.24 works again)
– POE-Component-Server-DNS has a bug which has been reported with a suggested fix (which has been tested with POE-Component-Server-DNS-0.30-fixed).

We have a new release, version 1.03 of Net::DNS.

This release contains work on Net::DNS’ Resolver. We now use IO::Socket::IP for better and more equally treated IPv6 support. Also the recursive part has, code-wise, been optimized.

This release has several very old Request Tickets resolved, which contained feature requests, for TCP support and persistent sockets for the Resolver::bg(send|read|isready) functions.

For a complete list of changes and bugfixes see the CHANGES file.