-
Notifications
You must be signed in to change notification settings - Fork 917
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
Comments
Recently upgraded to recursor 3.5.2, have been getting these in the log. The #15\010 seems consistent among the entries. pdns_recursor --versionversion: 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 nslookup -type=txt subway.com nslookup -type=txt mail2.moon-ray.com And a dkim one as well: |
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. |
dig TXT for dnscrypt records works after the change in 973efd3. This change will not go into 3.5.3. |
[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.
The text was updated successfully, but these errors were encountered: