Adding feature for local-data entries #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @DO1JLR,
I've added a feature to this Ansible role which allows the user to configure
local-data
entries insidethe Unbound configuration.
A basic template variable has been added with
This can also be left empty or omitted, the configuration will consider the state of these
variables. They will be only inserted if defined, so idempotency should be preserved.
Configuring the entries can be done via adding the DNS configuration entry into the list:
The host will receive an additional
local-data.conf
insideunbound.conf.d
if any entries exist.As of the nature of Unbound no CNAME/DNAME support is generally available (without stub-zones).
However, I added these because I also use a reverse-proxy and can configure individual domains there.
Within local networks I think this may be useful as we can define any arbitrary FQDN for some service running.
So adding some A entries for local networks is probably the main use-case for this
(or redirecting DNS queries to some other server on the Internet).