Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

win_dns_zone does not handle forwarders correctly #259

Closed
BoldlyGoingNoWhre opened this issue Jun 2, 2021 · 1 comment
Closed

win_dns_zone does not handle forwarders correctly #259

BoldlyGoingNoWhre opened this issue Jun 2, 2021 · 1 comment

Comments

@BoldlyGoingNoWhre
Copy link
Contributor

SUMMARY

Plays that have forwarders (non replicated) in them are not idempotent and fail to update

ISSUE TYPE
  • Bug Report
COMPONENT NAME

win_dns_zone

ANSIBLE VERSION
ansible 2.9.6
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/pvandepu/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.8.5 (default, Jan 27 2021, 15:41:15) [GCC 9.3.0]
CONFIGURATION
n/a
OS / ENVIRONMENT

target OS Windows 2021 R2

STEPS TO REPRODUCE
- name: Create DNS forwarder
      community.windows.win_dns_zone:
        name: myowndnszone.loc
        type: forwarder
        dns_servers:
          - 1.1.1.1
          - 2.2.2.2
EXPECTED RESULTS

DNS conditional forwarder zone is created / updated / unchanged if OK

ACTUAL RESULTS

DNS conditional forwarder zone is created if not exists (OK)
running the same play a second time results in error, running play with changed values results in error

FAILED! => {"changed": false, "msg": "Failed to set properties on the zone myowndnszone.loc: Cannot validate argument on parameter 'ReplicationScope'. The argument \"None\" does not belong to the set \"Forest,Domain,Legacy,Custom\" specified by the ValidateSet attribute. Supply an argument that is in the set and then try the command again."}
@jborean93
Copy link
Collaborator

This is fixed with #260.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants