We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We use pdns 3.1 (2607) as slave and we see several errors like:
pdns[777]: Exception building answer packet (Unable to parse DNS TXT '"v=spf1 a include:spf.emailfiltering.com all"') sending out servfail
The problem happens, when the - is not a hyphen-minus, but a UTF-8 encoded en-dash:
Fetching the record from the master (bind) works fine:
;; ANSWER SECTION: example.com. 3600 IN TXT "v=spf1 a include:spf.emailfiltering.com \226\128\147all"
Of course the SPF records seems to be wrong (copy-paste error).
But shouldn't pdns deliver the record although there is binary data?
The text was updated successfully, but these errors were encountered:
Author: peter duplicate of #541; the fix committed for 541 should fix your use case too. Closing this one.
Sorry, something went wrong.
Habbie
No branches or pull requests
We use pdns 3.1 (2607) as slave and we see several errors like:
pdns[777]: Exception building answer packet (Unable to parse DNS TXT '"v=spf1 a include:spf.emailfiltering.com all"') sending out servfail
The problem happens, when the - is not a hyphen-minus, but a UTF-8 encoded en-dash:
Fetching the record from the master (bind) works fine:
;; ANSWER SECTION:
example.com. 3600 IN TXT
"v=spf1 a include:spf.emailfiltering.com \226\128\147all"
Of course the SPF records seems to be wrong (copy-paste error).
But shouldn't pdns deliver the record although there is binary data?
The text was updated successfully, but these errors were encountered: