Hello,
Thanks for the report.
I've changed the dkim_create.sh to create 2048-bit keys.. that was the easy part.
The issue is that these longer keys exceed the max record length in named, so I had to go into over-kill mode to get DA to support over-sized records.
http://www.directadmin.com/features.php?id=1387
Code:
instead of this, which will break the zone:
value TXT "reallylongrecord"
it becomes:
value TXT ( "really"
"long"
"record" )
But it still displayed as the "reallylongrecord" in DA.
The bulk of the pre-release binaries are uploaded now (Check for a "./directadmin o" compile date of October 29th or newer.
The FreeBSD 6 32-bit, FreeBSD 7 64-bit, and Debian 5 32-bit build boxes are currently down, so they don't have the pre-release binaries updated yet.
The only issue I can see right now.. is that the record is so long that it makes the tables very ... very ... wide.
For now, it's not a major issue as it "works".. but we'll need to decide what's best to make it look nicer:
1) Make the font size 4.. essentially un-readable, but can still copy/paste correctly.
2) wrap the lines.. readable but the copy/paste wouldn't be accurate with the newline characters beraking it up.
3) Show the ( "really"
"long"
"record" )
just like it shows in the domain.com.db file (leaning towards this one). To edit or add a long record, you'd need to use the single "reallylongrecord" format, so going back and forth would be annoying.
4) Chop the value, and have a ">>" or "Show More" button in the record's td.. and when the button is clicked, the full value is shown.
Suggestions/input welcome.
John