DNS Text Label List Joiner
Join explicit DNS label octets into ASCII presentation text using decimal escapes for dots, backslashes and nonprintable octets; root is a single dot.
Description
Join explicit DNS label octets into ASCII presentation text using decimal escapes for dots, backslashes and nonprintable octets; root is a single dot.
DNS presentation text needs escaping when label octets contain dots, backslashes or nonprintable values. The absolute flag controls the final root dot.
When to use this tool
Join explicit DNS label octets into ASCII presentation text using decimal escapes for dots, backslashes and nonprintable octets; root is a single dot.
- Prepare the supplied labelsJson, absolute fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter labelsJson, absolute. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.name. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse labelsJson as DNS byte labels. Emit ordinary printable ASCII except dot and backslash literally; emit other octets as backslash plus three decimal digits. Join labels with dots and append a final dot when absolute; an empty list is allowed only for the absolute root.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| labelsJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
| absolute | Explicit choice for absolute; supply a boolean rather than a text label. | true or false |
For the JSON text fields, the following decoded structures show the example records before they are serialized into input strings. Keep field names, list nesting and value types as shown.
[
{
"field": "labelsJson",
"decoded": [
[
97,
46,
98
],
[
101
]
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.name | The name value under the stated formula or text convention. |
{
"input": {
"labelsJson": "[[97,46,98],[101]]",
"absolute": true
},
"output": {
"result": {
"name": "a\\046b.e."
}
}
}Limitations and assumptions
- The tool does not decode Unicode names or choose an IDNA policy. It formats supplied octets rather than querying DNS.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use a packet-aware DNS parser or resolver when the task requires compression-chain validation, live records or complete resource-record semantics. Keep byte labels, presentation text and network packets distinct.
References
Similar or alternative tools
- DNS Text Label List Splitter
Split ASCII DNS presentation text into explicit label octets with \DDD or escaped-character spelling; no Unicode IDNA conversion and root/absolute status is explicit.
- DNS Label ASCII Case Normalizer
Canonicalize DNS ASCII uppercase octets only, leaving non-ASCII bytes unchanged; does not apply Unicode lowercase or IDNA mappings.