[Pdns-users] Multipart TXT records
leen at consolejunkie.net
Mon Mar 1 19:07:21 UTC 2010
On 03/01/2010 04:53 PM, Chris Sarginson wrote:
> Thanks bert - there's a mention in one of the changelogs for pdns-backend-mysql rpms that this is supported (http://www.rpmfind.net/linux/RPM/opensuse/updates/11.0/x86_64/pdns-backend-mysql-2.9.21-143.5.x86_64.html and search for multi-part)
> Looks like it may be a Suse specific thing, but in the meantime I'll just increase the size of the content field.
I just checked it, it's not Suse specific, it just doesn't do/mean what
But atleast we now know it's not Suse specific. :-)
You can also see that here:
I'm unsure about what it does mean though.
My first thought would be that it's code to split large TXT-records over
Or just that multi TXT-records didn't work at all, a bug, as mentioned
in the log.
> -----Original Message-----
> From: bert hubert [mailto:bert.hubert at netherlabs.nl]
> Sent: 01 March 2010 15:48
> To: Chris Sarginson
> Cc: Pdns-users at mailman.powerdns.com
> Subject: Re: [Pdns-users] Multipart TXT records
> On Mon, Mar 01, 2010 at 03:44:04PM +0000, Chris Sarginson wrote:
>> Hi Bert
>>> Chris, try inserting the content in the database as one record, with content
>>> between quotes. I think it will split automatically. If it does not, split
>>> the data yourself.
>> The data is being split manually, as there is not sufficient space to
>> store as I've used the default db setup for MySQL, so the content field is
>> 255 character varchar - hence the 2 separate MySQL records in my original
> Ok - there is no support to join multiple rows in the database into one. You
> can however use alter table to stretch the content field.
> PowerDNS supports that explicitly.
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
More information about the Pdns-users