Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Unable to parse DNS TXT" logged by powerdns-recursor #795

Closed
ghost opened this issue May 10, 2013 · 3 comments
Closed

"Unable to parse DNS TXT" logged by powerdns-recursor #795

ghost opened this issue May 10, 2013 · 3 comments

Comments

@ghost
Copy link

ghost commented May 10, 2013

[This ticket was requested by Peter "Habbie" van Dijk.]

The following was logged:

pdns_recursor[18551]: STL error: Unable to parse DNS TXT '"k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDUghWyGRQ/MSWcNJhy2fAxrak/#15\010JTar6/pjfZNvf9CFFo6tfaUk+ooBiH5MUkochmE7Xl37Jq7A5tHhIPZZVWcTxRmf#015\010HxTFeLf4j6mN/bpkym2nxukGPdzPDIJWkhU/wUPT8+Nd/ouXyUDK0/eHskj4Wvr/#15\010AgeSl9Pjp2cfs1JytwIDAQAB"'

A tcpdump shows the query was targeted at variant4._domainkey.v4mail.co.uk.

PowerDNS recursor version (EPEL repository):

Name : pdns-recursor Relocations: (not relocatable)
Version : 3.5 Vendor: Fedora Project
Release : 1.el6 Build Date: Mon 15 Apr 2013 02:04:35 PM CEST
Install Date: Tue 07 May 2013 10:02:54 AM CEST Build Host: buildvm-24.phx2.fedoraproject.org
Group : System Environment/Daemons Source RPM: pdns-recursor-3.5-1.el6.src.rpm
Size : 1273790 License: GPLv2
Signature : RSA/8, Mon 15 Apr 2013 05:22:49 PM CEST, Key ID 3b49df2a0608b895

As a sidenote: It would be nice if the logging could be extended to include the source IP and the target domain of the query.

@bearggg
Copy link
Contributor

bearggg commented Jul 3, 2013

Recently upgraded to recursor 3.5.2, have been getting these in the log. The #15\010 seems consistent among the entries.

pdns_recursor --version

version: 3.5.2

Responds with a time out, and find these in syslog. Hope this helps track it down.

nslookup -type=txt _incspfcheck.mailspike.net
pdns_recursor[26972]: STL error (_incspfcheck.mailspike.net./16 from 173.244.96.86): Unable to parse DNS TXT '"v=spf1 exists:_h.%{h}._l.%{l}._o.%{o}._i.%{i}.spfcheck.mailspike.net ?all#015\010"'

nslookup -type=txt subway.com
pdns_recursor[26972]: STL error (subway.com./16 from 173.244.96.57): Unable to parse DNS TXT '"v=spf1 ip4:65.215.93.0/24 ip4:65.162.129.0/27 ip4:66.165.171.180 ip4:167.206.26.96/27 ip4:67.20.173.128/26 include:mailcontrol.com ptr:timon.subway.com ptr:jasper.subway.com include:msgfocus.com ?all#015\010 v=spf1 a:emailq.prizelogic.com ?all"'

nslookup -type=txt mail2.moon-ray.com
pdns_recursor[26972]: STL error (mail2.moon-ray.com./16 from 173.244.96.78): Unable to parse DNS TXT '"v=spf1 ip4:209.237.229.164 ip4:209.237.229.165#015\010ip4:209.237.229.162 ip4:209.237.229.163 #15\010 ip4:209.237.236.160 ip4:209.237.236.162 ip4:209.237.236.163#015\010ip4:209.237.236.161 ip4:209.237.236.165 ip4:209.237.236.166#015\010 a mx include:sendgrid.net ~all"'

And a dkim one as well:
nslookup -type=txt v1._domainkey.email.consumerreports.org
pdns_recursor[26972]: STL error (v1._domainkey.email.consumerreports.org./16 from 173.244.96.74): Unable to parse DNS TXT '"k=rsa;#15\010p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDFJC/V6DODV+euM3RWuRqqqJ3rNrV1DHgKxHtOxmZykAGvAsfYLsS98zTLhL2q/xteo8j3TBxIFoWqnzx/obqRMAXd7xLz+7xPOOuJhR5oozQpBfCuYY1CHSkol0ZGnU/qlyRLPPXl/bUL7V4FhwacjwScDUVuQtkcFiJ1BdgOWQIDAQAB"'

@Habbie Habbie reopened this Jul 4, 2013
Habbie pushed a commit that referenced this issue Aug 16, 2013
@Habbie
Copy link
Member

Habbie commented Aug 16, 2013

All these were fixed by the commit that initially closed this ticket, and that patch has now been merged into 3.5.3.

However, someone just reported that dig TXT 2.dnscrypt-cert.hallowe.lt @127.0.0.1 fails.

@Habbie
Copy link
Member

Habbie commented Aug 16, 2013

dig TXT for dnscrypt records works after the change in 973efd3. This change will not go into 3.5.3.

@Habbie Habbie closed this as completed Aug 16, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants