Diego Fronza 65f90f2927 Handling NoNameservers exception ... In the shutdown system test multiple queries are sent to a resolver instance, in the meantime we terminate the same resolver process for which the queries were sent to, either via rndc stop or a SIGTERM signal, that means the resolver may not be able to answer all those queries, since it has initiated the shutdown process. The dnspython library raises a dns.resolver.NoNameservers exception when a resolver object fails to receive an answer from the specified list of nameservers (resolver.nameservers list), we need to handle this exception as this is something that may happen since we asked the resolver to terminate, as a result it may not answer clients even if an answer is available, as the operation will be canceled. (cherry picked from commit b19cd2d83b)		2021-05-27 12:58:55 +10:00
..
ns1	Added test for the fix	2020-07-01 12:52:51 +02:00
ns2	Added test for the fix	2020-07-01 12:52:51 +02:00
resolver	add more logging to the shutdown system test	2020-10-01 18:09:35 +02:00
clean.sh	Disable pytest cacheprovider plugin in CI	2021-04-29 15:49:44 +02:00
conftest.py	update all copyright headers to eliminate the typo	2020-09-14 16:50:58 -07:00
prereq.sh	update all copyright headers to eliminate the typo	2020-09-14 16:50:58 -07:00
setup.sh	update all copyright headers to eliminate the typo	2020-09-14 16:50:58 -07:00
tests-shutdown.py	Handling NoNameservers exception	2021-05-27 12:58:55 +10:00