Hi,
Last week I discovered an issue with recursor v3.2.
It appears to return a malformed answer to the client in case the data (incl.
additional data) exceeds the 65536 maximum (2 bytes length field).
An example real-life lookup which has this issue as a result is MX of
auinmeio.com.br
When
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
I'm using pdns-3.0-rc1
if i dig www.clodo.ru on 188.127.244.30 like:
dig @188.127.244.30 www.clodo.ru A
first answer is correct:
cc00:~ # dig @188.127.244.30 www.clodo.ru A
; DiG 9.5.0-P2 @188.127.244.30 www.clodo.ru A
; (1 server found)
;; global options: printcmd
;; Got answer:
;;
On Mon, 2011-04-11 at 19:45 +0400, Vasiliy G Tolstov wrote:
I'm using pdns-3.0-rc1
if i dig www.clodo.ru on 188.127.244.30 like:
dig @188.127.244.30 www.clodo.ru A
In gpgsql database this domain does not exists.
pdns log contains:
2011-04-11T19:43:21.026760+04:00 selfip pdns[30873]: Query:
