Re: Generic records and DKIM
Matthew Dempsky <[email protected]>
| Newsgroups | gmane.network.djbdns |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Mar 18, 2009 at 11:47 AM, DAve <[email protected]> wrote: > Hmmm, so the cdb file created would have the data split? I tried it on a > test server, no change. Are you sure you recompiled tinydns-data and rebuilt the data.cdb using the new tinydns-data executable? If so, can you upload your data and data.cdb files somewhere that we can inspect them? > Surely I am not the only one serving DKIM from tinydns? The problem I was referring to isn't a tinydns limitation, it's a DNS limitation. A TXT record's data is split into chunks at most 255 bytes long. A base64 encoded 1536 or 2048 bit key will be larger than 255 bytes, so it'll necessarily span multiple chunks. If clients don't support concatenating chunks, then they can't support these larger keys. The immediate issue you're facing is that your DKIM software doesn't seem to support concatenating TXT record chunks, and because tinydns-data splits TXT records into somewhat smaller chunks than necessary, you're triggering that problem. Worst case, you use the generic format, but first I wanted to confirm this is actually necessary.