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
TXT entry more than 255 characters will cause SERVFAIL #1566
Comments
The definition of TXT RDATA is "One or more <character-string>s", i.e. a sequence in which each element is a <character-string> (which itself is "a single length octet followed by that number of characters… can be up to 256 characters in length (including the length octet)"). Not only is a single string with more than 255 octets of content invalid, it would be literally impossible to represent in wire format. See also #422 (which would have done a better job surfacing the underlying issue but was ultimately rejected) and #1428. |
Hello,
I wanted to know if there is any solution to send responses more than 255 characters other than splitting them into multiple responses?
Or at least send them in one response if separated:
Response when more than 255 characters:
Separated each 255 chars txt response:
Cloudns response:
I do know that there is no difference in processing them but in golang for example we have to join 2 separate txt lookups.
The text was updated successfully, but these errors were encountered: