Ansible Role: systemd-resolved
An Ansible role that configures systemd-resolved.
Table of Contents
Requirements
None.
Role Variables
Define your DNS servers:
systemd_resolved_servers:
- a.b.c.1
- a.b.c.2
systemd_resolved_fallback_servers:
- d.e.f.1
- d.e.f.2
Define your domains:
systemd_resolved_domains:
- example.com
Other variables in the order they show up along with their default values:
systemd_resolved_llmnr: 'yes'
systemd_resolved_multicast_dns: 'yes'
systemd_resolved_dnssec: 'allow-downgrade'
systemd_resolved_dns_over_tls: 'no'
systemd_resolved_cache: yes
systemd_resolved_dns_stub_listener: 'yes'
systemd_resolved_read_etc_hosts: yes
For more information, read man 5 resolved.conf
.
Dependencies
None.
Example Playbook
Add to requirements.yml
:
---
- src: idiv-biodiversity.systemd_resolved
...
Download:
$ ansible-galaxy install -r requirements.yml
Top-Level Playbook
Write a top-level playbook:
---
- name: head server
hosts: head
roles:
- role: idiv-biodiversity.systemd_resolved
tags:
- systemd-resolved
...
Role Dependency
Define the role dependency in meta/main.yml
:
---
dependencies:
- role: idiv-biodiversity.systemd_resolved
tags:
- systemd-resolved
...
License
MIT
Author Information
This role was created in 2019 by Christian Krause aka wookietreiber at GitHub, HPC cluster systems administrator at the German Centre for Integrative Biodiversity Research (iDiv).