DNS Name Absolute from Relative
Append explicit relative DNS label octets to a zone’s labels with complete-name byte-budget validation; no resolver, search-list or origin guessing.
Description
Append explicit relative DNS label octets to a zone’s labels with complete-name byte-budget validation; no resolver, search-list or origin guessing.
An explicitly relative DNS label sequence becomes absolute by appending a chosen zone suffix. Keeping labels as octets avoids ambiguous dot escaping.
When to use this tool
Append explicit relative DNS label octets to a zone’s labels with complete-name byte-budget validation; no resolver, search-list or origin guessing.
- Prepare the supplied relativeJson, zoneJson 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 relativeJson, zoneJson. 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.labels. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse relativeJson and zoneJson as label-byte arrays, concatenate them in that order and require the uncompressed name budget, including length bytes and root zero, to fit 255 bytes.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| relativeJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
| zoneJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
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": "relativeJson",
"decoded": [
[
97
]
]
},
{
"field": "zoneJson",
"decoded": [
[
98
],
[
99
]
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.labels | The labels list in the ordering and representation described above. |
{
"input": {
"relativeJson": "[[97]]",
"zoneJson": "[[98],[99]]"
},
"output": {
"result": {
"labels": [
[
97
],
[
98
],
[
99
]
]
}
}
}Limitations and assumptions
- The zone is supplied explicitly. No resolver search list, Unicode IDNA conversion or origin guessing is performed.
- 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 Name Relative to Zone
Return exact relative DNS labels only for a name inside an explicitly supplied zone suffix; outside names remain null and case is preserved.
- DNS Name Longest Common Suffix
Find the longest complete DNS label suffix shared by two names under ASCII case-insensitive comparison, preserving the left name’s original octets.