New Feature: ContinueOnEmptyResponse setting #128
MichaCo
started this conversation in
Show and tell
Replies: 0 comments
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
-
In version 1.2.0,
LookupClient
stops querying any other server in case the response was valid.Valid responses are any responses without an error code. (Error responses might be retried, depending on configuration...)
But a no-error response might have zero answers, which can have many reasons.
It is very likely that every DNS server in your network will return the same empty response, but there are some network configurations where DnsClient will auto-resolve servers from multiple network adapters which might not return the same result.
So, it might make sense to try the other servers anyways.
Starting with version 1.3.0 of DnsClient,
LookupClient
will now try to find an answer from all configured DNS servers (per default).The logic here is relatively simple:
(this part is ignored if the question is either
ANY
orAXFR
)The behavior can be disabled with a new setting called
ContinueOnEmptyResponse
.I don't think this will change anything for most use-cases, as most setups usually just resolve one NameServer anyways, like in most VMs or containers.
Example
Log output
Result
Beta Was this translation helpful? Give feedback.
All reactions