summaryrefslogtreecommitdiff
path: root/doc/forum/DNS_-_Support_for_Multiline_TXT_records/comment_1_b97c158ae4e3abb6e4c90a2c91e0c207._comment
blob: 5595af19a02848f64d6a930692ae3efe19e48b1e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
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.
"""]]