Proper Encoding/Decoding for Email Name Representation for SOA and RP Records #93
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.
According to RFC 1035 (but initially defined in RFC 883), email addresses can be represented as domain names in SOA (RNAME) and RP (MBOX) Records. An email address consists of two parts, a local part and the domain (
<local part>@<domain>
). Currently,dns-packet
does not support proper processing of email addresses if the local part contains dots (.
). E-mail DNS labels in the local part are allowed to contain a dot, which must be escaped by\.
in the representation format. With wire format, the label size is simply set to span the entire label, including all dots.SOA (RFC 1035):
RP (RFC 1183):
dig example:
dns-packet example after this change:
peter\.van\.dijk.powerdns.com
->peter.van.dijk@powerdns.com
This PR should also fix #90