Skip to content
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

DNS Query Forward not appearing in UI #49

Open
tomjones1977 opened this issue May 14, 2024 · 1 comment
Open

DNS Query Forward not appearing in UI #49

tomjones1977 opened this issue May 14, 2024 · 1 comment

Comments

@tomjones1977
Copy link

The opnsense_unbound_forward (Resource) correctly configures a query forward to an internal DNS server, but the record does not appear anywhere in the UI:

opnsense_unbound_forward.query: Creating...
opnsense_unbound_forward.query: Creation complete after 2s [id=5a8fc7f3-5040-482e-86e8-8cfa3ac3b274]

image

@browningluke
Copy link
Owner

Hi there @tomjones1977, thanks for opening this issue!

Firstly, if you re-run terraform apply, does it want to recreate the resource? (i.e. did the provider correctly create the resource). If it does try to recreate it, let me know because there might be a bug with the mutex locking.

However, it's probably due to the fact that the provider creates forwards using Unbound's DNS over TLS section:
image

This is because the DoT section is a superset of the old Query Forwarding section. To create a regular DNS Query Forward:

// Query Forward
resource "opnsense_unbound_forward" "query" {
  domain = "example.lan"
  server_ip = "192.168.1.2"
  server_port = 53 # set this to 53 (which forwards as expected, or omit the parameter to default to 53)
}

I suspect you've already configured everything correctly, but just aren't looking under the /ui/unbound/dot section of the UI. This is probably a fault of the documentation and I will update it to make it more clear.

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

No branches or pull requests

2 participants