This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
extensions:teemip-zone-mgmt [2024/04/04 12:51] – [TXT Records] cnaud | extensions:teemip-zone-mgmt [2024/04/04 13:01] – [TXT Records] cnaud | ||
---|---|---|---|
Line 489: | Line 489: | ||
=== TXT Records with a payload over 255 chars == | === TXT Records with a payload over 255 chars == | ||
- | A TXT record may have more than 255 characters of data, but **not** more than 255 characters in a single string, which is problematic for long chains like DKIM keys. RFC 4408 defines how to get around this limitation : a TXT record is allowed to contain multiple strings which should then be concatenated together by the reading application. TeemIP implements this concept through a chaining mechanism. TXT records with the **exact same** RR Name may be chained together. | + | A TXT record may have more than 255 characters of data, but **not** more than 255 characters in a single string, which is problematic for long chains like DKIM keys. RFC 4408 defines how to get around this limitation : a TXT record is allowed to contain multiple strings which should then be concatenated together by the reading application. TeemIP implements this concept through a chaining mechanism. |
<note tip> | <note tip> | ||
Line 496: | Line 496: | ||
* If **Next segment** of record R1 is set to R2, then **Previous segment** of record R2 will be set to R1 | * If **Next segment** of record R1 is set to R2, then **Previous segment** of record R2 will be set to R1 | ||
</ | </ | ||
+ | <note warning> | ||
+ | In a chain, only the RR Name of the **first segment** is relevant. It is considered as the reference of the record when the db file is built. The name of the following records of the chain are just used for reference. | ||
+ | </ | ||
{{ classupdate_txtrecord3x-2.png }} | {{ classupdate_txtrecord3x-2.png }} | ||
- | The tool that generate Zone data files will take the chain into consideration and will create the proper entry in the db file. | + | The tool that generate Zone data files will take the chain into consideration and will create the proper entry in the db file as shown in the exemple below. |
+ | |||
+ | {{ dbfile_long_txtrecord.png }} | ||
==== Generic Records ==== | ==== Generic Records ==== |