-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add field(s) representing DNS header flags #9
Comments
I can see two ways of doing this:
Alternatively the values of interest could be added as I think the amount of work to add these values does not make a lot of difference from the rec point of view. Methods 2 is more compact of course, but does involve work for the client to decode. Encoding in |
Thanks Otto. I lean toward option 2, mainly because it means we don't have to do any additional work in future to add for example new EDNS0 flags, even if that does mean a bit more work on behalf of the protobuf client. Adding in |
Currently we add nothing to |
I think dnsdist could also potentially add these fields? |
yes, atm only configurable in |
There are various DNS flags that are not represented in the protobuf dnsmessage. For example Recursion Desired (RD), Recursion Available (RA), Truncated Response (TC) etc.
It would be good if these were available in the protobuf in some form, specifically:
AA, RD, RA, TC, AD, CD (from regular DNS header flags)
And also it would be nice if the protobuf indicated:
The text was updated successfully, but these errors were encountered: