mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-04-10 12:40:31 -07:00
d9d9148510
dig lookup plugin: Fix using only last nameserver specified (#8970)
* dig plugin: Fix using only last nameserver given
Currently, when specifying multiple nameservers
either using multiple `@ns.example.com` arguments
or by specifying multiple nameservers in a single
argument (@ns1.example.com,ns2.example.com), due
to a bug only the very last nameserver that is
specified is actually used.
This is because for every iteration of the
for ns in nsset
loop, the local list of nameservers is cleared
and after adding the currently processed nameserver
entry, the whole `nameservers` list of the Resolver
instance is overridden with that new list with just
one element. And as far as I can see, when setting
that `nameserver` property, the dnspython library
actually overrides the existing list and doesn't
do some trickery to append the new nameservers or
something like that.
Therefore, the assignment of the `nameservers`
property of the Resolver is moved after the argument
processing so all nameservers are added and then
collectively written to the `nameservers` property
of the Resolver.
* Add CHANGELOG fragment
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| .keep | ||
| 8.6.6.yml | ||
| 8785-keycloak_user_federation-set-krbPrincipalAttribute-to-empty-string-if-missing.yaml | ||
| 8812-keycloak-user-federation-remove-lastSync-param-from-kc-responses.yml | ||
| 8877-keycloak_realm-sort-lists-before-change-detection.yaml | ||
| 8887-fix-one_service-unique.yml | ||
| 8900-ipa-hostgroup-fix-states.yml | ||
| 8925-atomic.yml | ||
| 8970-fix-dig-multi-nameservers.yml | ||