[Pdns-users] Recursor v3.2 and v3.3 malformed answer in case of big response from authoritative

bert hubert bert.hubert at netherlabs.nl
Mon Apr 11 15:11:41 UTC 2011

On Mon, Apr 11, 2011 at 04:53:16PM +0200, Thor Spruyt wrote:
> Last week I discovered an issue with recursor v3.2.

This is probably fixed in 3.3.1:
Discovered by John J and Robin J, the PowerDNS Recursor did not process
packets that were truncated in mid-record, and also did not act on the
'truncated' (TC) flag in that case. This broke a very small number of
domains, most of them served by very old versions of the PowerDNS
Authoritative Server. Fix in commit 1740.

3.3.1 has not been formally released, but is in wide production and can be
found on http://svn.powerdns.com/snapshots/pdns-recursor-3.3.1.tar.bz2

3.3.1 here resolves auinmeio.com.br|MX just fine, although it takes a
stunning 193 packets (!!).

However, it does end up delivering a slightly weird answer, which we are
investigating (trailing bytes).

Can you open a ticket on http://wiki.powerdns.com? 


More information about the Pdns-users mailing list