As it turns out, the answer is yes, Stream does in fact report DNS query events backwards. Each DNS record comes with two times; "timestamp", the start of the DNS session and "endtime", the end of the session. The default props.conf sets _time to "endtime", which produces the appearance of the backwards DNS events.
For example, if a workstation makes a DNS request through an internal DNS server who then passes the request to an external server you would expect to see
Workstation => Internal DNS
Internal DNS => External DNS
Internal DNS => External Authoritative DNS
However, since the workstation technically has the longest time to wait for its session to complete it will appear as
1. Internal DNS => External Authoritative DNS
2. Internal DNS => External DNS
3. Workstation => Internal DNS
... View more