Designate/pdns breaks at semicolons in DNS record TXT values
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
New
|
Undecided
|
Unassigned |
Bug Description
Downstream report: https:/
To reproduce the problem, I tried to make a TXT record called "designatetesti
It went in fine and Horizon shows it fine, but look what happens when I ask pdns about it:
alex@alex-laptop:~$ dig designatetestin
; <<>> DiG 9.11.3-
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39511
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 2800
;; QUESTION SECTION:
;designatetesti
;; ANSWER SECTION:
designatetestin
;; Query time: 197 msec
;; SERVER: 208.80.
;; WHEN: Tue Aug 28 23:51:28 BST 2018
;; MSG SIZE rcvd: 82
It (either pdns or designate) found the first semicolon and stopped there.
I believe that's mitaka. I can ask for details of the installation from it's administrators if that would be helpful.
probably related to https:/ /bugs.launchpad .net/designate/ +bug/1755788