This file contains al notable changes to the bertvv.dnsmasq
Ansible role.
This file adheres to the guidelines of http://keepachangelog.com/. Versioning follows Semantic Versioning.
- (GH-8) Specify upstream DNS servers with
dnsmasq_upstream_servers
(credits to Niklas Juslin) - (GH-8) Specify SRV records with
dnsmasq_srv_hosts
(credits to Niklas Juslin)
- Support for Fedora, including tests (on Fedora 23).
Some of the changes below result in different default behaviour of the role compared to previous version. These are considered breaking backwards compatibility, hence the major version increment.
- Make
dnsmasq_listen_address
optional. This changes the default behaviour into listening to all interfaces. - Enable
dnsmasq_bogus_priv
by default for better security. - Enable
dnsmasq_domain_needed
by default for better security. - Use generic ‘package’ module for installation. This is a feature new in Ansible 2.0, so this version of the role can no longer be used on older versions of Ansible. This is also considered as a breaking change.
- Separated test code into a different branch,
tests
.
- Functional tests (with BATS)
- The
version:
field inmeta/main.yml
was removed because it is no longer accepted in Ansible 2.0. Unfortunately, this change breaks compatibility withlibrarian-ansible
. For more info on this issue, see ansible/ansible#.
- Role variable
dnsmasq_interface
(credits to David Wittman) - Role variable
dnsmasq_server
(credits to David Wittman)
- Setting firewall rules. This should not be a concern of this role. Use another role that manages the firewall specific to your distribution (e.g. bertvv.el7).
- Role variable
dnsmasq_authoritative
: when true, dnsmasq will function as an authoritative name server. (credits to Chris James) - Config files in
/etc/dnsmasq.d/
will now also be read
- Fixed typo (credits to Chris James)
- Role test with Vagrant
- Remodeled firewall rules
- Updated documentation
- Coding style: use valid YAML instead of Ansible specific
var=val
syntax.
- DNS forwarding
- DHCP server