Hey Jullan,
Thank you for the reply -- my problem isn't how to compose a
multi-part SPF message inside a TXT record.
The problem I see is how PowerDNS (mis-)behaves when trying to serve a
non-compliant record.
PowerDNS returns NOERROR for the status and then returns a malformed message.
I
Augie Schwer wrote:
PowerDNS returns a malformed response when queried for a TXT record
larger than 257 characters.
[...]
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
I wrote:
The problem is that while a TXT record can contain multiple strings
(the parts you have to enclose in double quotes in TXT records in both
BIND and PowerDNS), each string can only be 256 bytes long at maximum
by design -- one length octet plus 255 bytes of text (RFC 1035). If
you
