> On Mar 20, 2019, at 19:37, Jonathan Reed wrote:
>
> >> TXT records are limited to strings of 255 characters or less, but can have
> >> multiple strings, They'll be concatenated in order by the DKIM validator -
> >> I'm guessing that's what you're thinking of.
> > Yes, indeed.
> >
> > My pub
On Mar 20, 2019, at 19:37, Jonathan Reed wrote:
>> TXT records are limited to strings of 255 characters or less, but can have
>> multiple strings, They'll be concatenated in order by the DKIM validator -
>> I'm guessing that's what you're thinking of.
> Yes, indeed.
>
> My pub key is 400 cha
>
> TXT records are limited to strings of 255 characters or less, but can have
> multiple strings, They'll be concatenated in order by the DKIM validator -
> I'm guessing that's what you're thinking of.
Yes, indeed.
My pub key is 400 chars long, and inserting the long string as a set into
records
> On Mar 20, 2019, at 5:49 PM, Jonathan Reed wrote:
>
> Hi,
>
> I'm running an old version of pdns where my backend record length for
> "records.name" is still varchar(255). I've read it's been extended to 64k.
> However I'm trying to insert a 400 character dkim value in it by adding
> mult
Hi,
I'm running an old version of pdns where my backend record length for "
records.name" is still varchar(255). I've read it's been extended to 64k.
However I'm trying to insert a 400 character dkim value in it by adding
multiple records for the dkim to simulate a continuation of the key string.
