#3113 Maximum length for DNS TXT records is not enforced
Closed: wontfix 5 years ago Opened 11 years ago by pspacek.

Maximum data length for single TXT record is 255 bytes. See [RFC 1035 section 3.3.14] and http://tools.ietf.org/html/rfc1035#section-3.3 section 3.3.

User interface has to enforce this limit for all record manipulations.

Because of DNS escaping, following records are equivalent. Both records have maximal length:

test.test.      86400   IN  TXT "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde"
test.test.      86400   IN  TXT "\048123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde"

DNS escaping is described in RFC 1035 page 35.


Moving my tickets back to free-to-take pool.

Metadata Update from @pspacek:
- Issue assigned to someone
- Issue set to the milestone: Ticket Backlog

7 years ago

Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.

Metadata Update from @rcritten:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata