Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
0x7F char causes "Unable to parse DNS TXT" in powerdns-recursor #1727
When the latest powerdns-recursor version (3.6.1) attempts to resolve a TXT record containing the character 0x7F (DEL), it errors out (see error below). This is because 837f4b4 was an incomplete fix: "> 127" should be replaced with "> 126".
STL error: Unable to parse DNS TXT '"\x7f"'
Any update? It is a one-line patch to fix this issue... I created a record to help you guys test and validate the fix. If x.x.x.x is a PowerDNS resolver run:
$ dig @x.x.x.x -t txt bug.zorinaq.com
Actual result: dig times out... and pdns_recursor logs show "Unable to parse DNS TXT '"\x7f"'
Expected result: dig showing:
; <<>> DiG 9.9.5-3-Ubuntu <<>> @x.x.x.x -t txt bug.zorinaq.com
;; OPT PSEUDOSECTION:
;; ANSWER SECTION:
As Habbie said, the patch is described in the first post on this page (replacing "> 127" with "> 126" at line 395 of this patch: 837f4b4).
I built 3.6.1 on Ubuntu 14.04 with a simple ./configure && make (and running pdns-recursor from the source tree.) Although it has been 2 weeks since I did it so I don't recall the exact details and did not take notes other than submitting this bug. I will double-check tonight my steps...