DNS transaction handling issues
We don't properly handle the case where many requests are lost:
1. transaction_max not (always?) incremented
2. no 'request lost' flag
Updated by Jason Ish about 7 years ago
- Status changed from Assigned to Closed
- Target version changed from 70 to 3.1.1
The use of different logger contexts for requests and replies should resolve this as the transaction log handling only concerns itself with a single direction, so lost messages should not affected future transactions.