PowerDNS returns a malformed response when queried for a TXT record larger than 257 characters.
dig +short txt 258txt.schwer.us @a.auth-ns.sonic.net ;; Warning: Message parser reports malformed message packet. PowerDNS Authoritative version 2.9.22 Record in the DB looks like this : 258txt.schwer.us | TXT | "v=spf1 ip4:209.204.164.194 a mx mx:gordonmedical.com, mx:mailin-02.mx.sonic.net, mx:g.mx.sonic.net, mx:mailin-01.mx.sonic.net, mx:e.mx.sonic.net, mx:a.mx.sonic.net, mx:c.mx.sonic.net, mx:d.mx.sonic.net, mx:h.mx.sonic.net, mx:f.mx.sonic.net, mx:and mx:b.mx." PowerDNS returns NOERROR and returns as much data as it can which ends up creating the corrupt packet. Admittedly one shouldn't put bad data in (the above record is not RFC compliant); I was hoping PowerDNS would handle the response better -- any of the response codes could fit and certainly not return a malformed packet; I'd rather see an empty packet or maybe a truncated RDATA and a NOERROR return code. Thoughts? -- Augie Schwer - au...@schwer.us - http://schwer.us Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072 _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
