You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would there be interest in patches to add a RFC8427 output mode to ldns, and to drill? As in: if someone else does the work, would it be accepted for merging into ldns/drill ?
If the answer is "yes", I can try to propose this to my manager...
Note that any such support would likely require adding a json output library (probably json-c), as a dependency, though. The whole thing would be optional (i.e. json lib not available, or feature not requested in build would cause the json-format code and dependencies to be ignored during build).
Currently, we're parsing dig/drill output to get structured data out of it, but that's... annoying to say the least. Getting proper structured output right out of the tool would be better. getdns has something like this, but it is way too heavy and predates RFC8427, so it is non-standard and uninteresting for our purposes...
The text was updated successfully, but these errors were encountered:
Hah, I will propose it to my managers, let's see what their reply is. Might take quite a while, though, but at least your reply makes it a real possibility...
Would there be interest in patches to add a RFC8427 output mode to ldns, and to drill? As in: if someone else does the work, would it be accepted for merging into ldns/drill ?
If the answer is "yes", I can try to propose this to my manager...
Note that any such support would likely require adding a json output library (probably json-c), as a dependency, though. The whole thing would be optional (i.e. json lib not available, or feature not requested in build would cause the json-format code and dependencies to be ignored during build).
Currently, we're parsing dig/drill output to get structured data out of it, but that's... annoying to say the least. Getting proper structured output right out of the tool would be better. getdns has something like this, but it is way too heavy and predates RFC8427, so it is non-standard and uninteresting for our purposes...
The text was updated successfully, but these errors were encountered: