From 16e029099f0be3491e9d7ad6f787cd24d5ef58bf Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 23 Jun 2018 15:11:34 -0400 Subject: response --- ...ent_1_b97c158ae4e3abb6e4c90a2c91e0c207._comment | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 doc/forum/DNS_-_Support_for_Multiline_TXT_records/comment_1_b97c158ae4e3abb6e4c90a2c91e0c207._comment (limited to 'doc/forum/DNS_-_Support_for_Multiline_TXT_records') diff --git a/doc/forum/DNS_-_Support_for_Multiline_TXT_records/comment_1_b97c158ae4e3abb6e4c90a2c91e0c207._comment b/doc/forum/DNS_-_Support_for_Multiline_TXT_records/comment_1_b97c158ae4e3abb6e4c90a2c91e0c207._comment new file mode 100644 index 00000000..5595af19 --- /dev/null +++ b/doc/forum/DNS_-_Support_for_Multiline_TXT_records/comment_1_b97c158ae4e3abb6e4c90a2c91e0c207._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2018-06-23T18:42:32Z" + content=""" +It seems that the limit is 255 characters, and this +limit applies to any string in a bind zone file, +rather than being a maximim line length. A single line can contain multiple +such strings, although there's probably a maximum line length somewhere +too, so using parens to extend across multiple lines is wise. + +The values inside the parens are concacenated together, no newline is added +to the string that bind builds up from them AFAICS. + +So it seems your code is stripping out the newlines from the TXT value. +Which probably doesn't matter for DKIM public key material, +and I don't think that bind zone files support multiline strings anyway. +But a single line could be too long and splitting on newlines would not +help then. + +So, I think the thing to do would be to make `rValue` break TXT +strings into substrings no longer than 255 characters. Then you don't +need a new constructor, and long SSHFP etc records could also be handled +that way. +"""]] -- cgit v1.2.3