Skip to content

Adding feature for local-data entries #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

AkaBlur
Copy link

@AkaBlur AkaBlur commented Jul 5, 2025

Hi @DO1JLR,

I've added a feature to this Ansible role which allows the user to configure local-data entries inside
the Unbound configuration.


A basic template variable has been added with

# list of optional local-data entries
unbound__local_data: []

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:

unbound__local_data: [
  "homeassistant.local A 10.0.0.25",
  "gitea.local A 10.0.0.20"
]

The host will receive an additional local-data.conf inside unbound.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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant