ansible-role-systemd-resolved's Introduction

Ansible Role: `aisbergg.systemd_resolved`

Configures systemd-resolved as a network name resolution manager on Linux systems.

Requirements

System needs to be managed with Systemd

Role Variables

Variable	Default	Comments
`systemd_resolved_service_enabled`	`yes`	Enables the `resolved` service.
`systemd_resolved_service_state`	`started`	The state of the serice to be in.
`systemd_resolved_config`	`{}`	The configuration for `resolved`. Full documentation of all parameters can be found in resolved.conf(5).
`systemd_resolved_config.DNS`	`[]`	List of IPv4 and IPv6 addresses to use as system DNS servers.
`systemd_resolved_config.FallbackDNS`	`[]`	List of IPv4 and IPv6 addresses to use as the fallback DNS servers.
`systemd_resolved_config.Domains`	`[]`	List of domains to use as search suffixes when resolving single-label host names.
`systemd_resolved_config.LLMNR`	`yes`	Controls Link-Local Multicast Name Resolution support on the local host.
`systemd_resolved_config.MulticastDNS`	`no`	Controls Multicast DNS support on the local host.
`systemd_resolved_config.DNSSEC`	`no`	Enables DNSSEC-validation for DNS lookups.
`systemd_resolved_config.DNSOverTLS`	`no`	Enables encryption for DNS lookups.
`systemd_resolved_config.Cache`	`yes`	Use cache for DNS lookups.
`systemd_resolved_config.DNSStubListener`	`yes`	Enable DNS stub resolver to listen on 127.0.0.53 port 53.
`systemd_resolved_config.ReadEtcHosts`	`yes`	Read /etc/hosts and to resolve hosts.

Dependencies

None.

Example Playbook

- hosts: all
  vars:
    systemd_resolved_config:
      DNS:
        - 9.9.9.9
        - 8.8.8.8
      Domains:
        - example.org
  roles:
    - role: aisbergg.systemd_resolved