Aram Sargsyan 8611aa759f DiG: use the same retry and fail-over logic for different failure types ... DiG implements different logic in the `recv_done()` callback function when processing a failure: 1. For a timed-out query it applies the "retries" logic first, then, when it fails, fail-overs to the next server. 2. For an EOF (end-of-file, or unexpected disconnect) error it tries to make a single retry attempt (even if the user has requested more retries), then, when it fails, fail-overs to the next server. 3. For other types of failures, DiG does not apply the "retries" logic, and tries to fail-over to the next servers (again, even if the user has requested to make retries). Simplify the logic and apply the same logic (1) of first retries, and then fail-over, for different types of failures in `recv_done()`.		2022-07-22 08:35:35 +00:00
..
ns2	Upgrade uses of hmac-md5 to DEFAULT_HMAC	2022-07-07 10:11:42 +10:00
ns3	Use DEFAULT_HMAC for rndc	2022-07-07 10:11:42 +10:00
ns4	Use DEFAULT_HMAC for rndc	2022-07-07 10:11:42 +10:00
clean.sh	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
setup.sh	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
tests.sh	DiG: use the same retry and fail-over logic for different failure types	2022-07-22 08:35:35 +00:00