fortios_system_dns about ansible-galaxy-fortios-collection

[JieX19]

Hi @RichardBotham,

Can you please check the runtime module is the one in galaxy collection not the old ansible module? I've noticed hosts, username, password, ssl_verify, https parameters used in the playbook, they'are actually causing the issue you mentioned above.

We use ansible_httpapi_use_ssl [yes/no] and ansible_httpapi_validate_certs [yes/no] instead in collection. And please note if you're using hosts, username, password in the playbook, then the old ansible modules will be called not the ones in collection.

FYI, here's a workable playbook.

- hosts: fortigateslab
  connection: httpapi
  collections:
    - fortinet.fortios
  vars:
    ansible_httpapi_use_ssl: yes
    ansible_httpapi_validate_certs: no
    ansible_httpapi_port: 443
    vdom: "root"
  tasks:
  - name: Configure DNS.
    fortios_system_dns:
      vdom:  "{{ vdom }}"
      system_dns:
        source_ip: "192.168.127.110"
        domain:
          - 
            domain: "bbc.co.uk"

You can config the hosts file under /etc/ansible/hosts and no need to use them in the playbook.

[fortigateslab]
fortigate01 ansible_host=192.168.190.100 ansible_user="admin" ansible_password="password"

[fortigateslab:vars]
ansible_network_os=fortinet.fortios.fortios

[chillancezen]

@RichardBotham hi Rich,

httpapi is preferred as Jie suggested.

but first make it clear which fortios version it is and install correct fortios collection.
Let's continue to use https://fndn.fortinet.net/index.php?/forums/topic/2269-ansible-and-fortios_system_dns/ to track this issue.

I mark this closed.

thanks,
Link