TXT record data length limit is too short
Bug #1595265 reported by
Paul Glass
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Low
|
Emanuel Andrecut |
Bug Description
A similar bug is reported here as "fixed" https:/
Changed in designate: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in designate: | |
assignee: | nobody → Emanuel Andrecut (andrecutm) |
status: | Triaged → In Progress |
To post a comment you must log in.
Some notes on this:
<mugsie> #topic bug triage meeting- alt to: "bug triage (Meeting topic: Designate)" /bugs.launchpad .net/designate/ +bug/1595265 fedora/ sdake) has joined #openstack- meeting- alt 232.sub- 72-104- 180.myvzw. com) has joined #openstack- meeting- alt /bugs.launchpad .net/designate/ +bug/1474012 is closed alright fedora/ sdake) has quit (Ping timeout: 246 seconds) meeting- alt 97-100- 220-44. res.bhn. net) has joined #openstack- meeting- alt 232.sub- 72-104- 180.myvzw. com) has quit (Ping timeout: 250 seconds) _netblocks. google. com include: _netblocks2. google. com include: _netblocks3. google. com ~all"</sidenote> fen@nat/ intel/x- ygbwirwmlwnwrhs i) has quit (Remote host closed the connection)
* openstack has changed topic for #openstack-
<timsim> https:/
<openstack> Launchpad bug 1595265 in Designate "TXT record data length limit is too short" [Undecided,New]
<Kiall> I think we already have a bug for that
<mugsie> its closed
<Kiall> No, a diff one
<Kiall> 1 sec
<mugsie> oh
--> sdake_ (~sdake@
--> tango (~tonanhngo@
<Kiall> https:/
<openstack> Launchpad bug 1474012 in Designate "Incorrect length limit for TXT record data" [Medium,Fix committed] - Assigned to Federico Ceratto (federico-ceratto)
<mugsie> I think this is more of a feature req ?
<-- Sukhdev (~<email address hidden>) has quit (Quit: My Mac has gone to sleep. ZZZzzz…)
<federico3> since quite a while
<Kiall> So - I think it's a rather large change to make it work with longer than 255 chars
<mugsie> yeah
<timsim> Kiall: We don't use a varchar(255) col for it
<Kiall> Technically, we support only single part TXT recrods, where each part is at most 255 charas
<mugsie> as it will change who it is stored, and how we conncatinate it in mdns
<Kiall> anything more needs to be split in the DNS wire format response... but.. where do we split?
<-- sdake (~sdake@
<Kiall> i.e. TXT is defined as an array of strings, each up to 255 chars long.
<Kiall> we don't have it modeled as an array
<timsim> So we'd have to split it every 255 into multiple records?
<timsim> oh i see
<mugsie> I dont think we can target this to a particular relase anyway
<Kiall> Not multiple records, just in the TXT's rdata
<mugsie> we can mark it as low ?
<mugsie> and if someone has cycles, propose a spec to show how we can fix it?
<Kiall> i.e. foo.com. IN TXT "255 chars" "255 chars" "255 chars"
<timsim> pglass what was the thing that made us run into this?
--> sarob (~<email address hidden>) has joined #openstack-
--> cleong (~corey@
<pglass> uhh, it's not big enough for spf records or something
<Kiall> <sidenote>Use SPF inclides</sidenote>
<Kiall> includes*
<Kiall> We *may* be able to hard split on 255, or split on word boundaries, or something.. but I've no clue how valid that is
<-- tango (~tonanhngo@
<mugsie> Kiall: can you dump ^ into the bug?
<-- sarob (~<email address hidden>) has quit (Remote host closed the connection)
<mugsie> and say we will want a spec for any fix
<Kiall> <sidenode> SPF includes look like this.... _spf.google.com. 295 IN TXT "v=spf1 include:
<-- shaohe_feng (shaohe_
--> sarob (~sarob@m...