Support escaping literal dots and special characters in domain names #144
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Among others, this is needed for PTR records for DNS-based service discovery (DNS-SD) that contain "human friendly" names. The backslash-escaping allows literal dots in the name (escaped) to be distinguished from label-separator dots (not escaped). See https://tools.ietf.org/html/rfc6763#section-4.3
jsor
approved these changes
Aug 7, 2019
WyriHaximus
approved these changes
Aug 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Among others, this is needed for PTR records for DNS-based service
discovery (DNS-SD) that contain "human friendly" names. The
backslash-escaping allows literal dots in the name (escaped) to be
distinguished from label-separator dots (not escaped).
See https://tools.ietf.org/html/rfc6763#section-4.3