Add the client transport to the output from "rndc recursing"
Description
When investigating a problem with increasing numbers of recursing clients, it's routine to dump the backlog list using control command "rndc recursing" so that an inspection can be made of the clients and queries that persisting for longer than expected.
The objective is to look for 'patterns' in clients and queries to try to identify the root cause (whether it be query-related, code-related, process-related or something to do with the clients themselves).
At the moment, we are given the client, the actual query and the time of the query - but we don't know what transport the client query is using. For troubleshooting purposes, this could be significant because of the different processing paths taken (particularly on timeouts) for the different transports.
Request
Please add a new column to "rndc recursing" output that provides the client transport (UDP, TCP etcetera).