Home
Help
Search
Login
Register
OPNsense Forum
»
English Forums
»
General Discussion
»
Unbound stopped resolving
« previous
next »
Print
Pages: [
1
]
Author
Topic: Unbound stopped resolving (Read 569 times)
tl5k5
Jr. Member
Posts: 50
Karma: 0
Unbound stopped resolving
«
on:
April 03, 2023, 05:41:56 pm »
I posted this back on March 23rd in the 23.1 forum but since there were no replies, I thought I'd post it here.
This morning I started the day with 22.7.11 running on one of my proxmox servers.
We started noticing some webpages weren't accessible. It progressively got worse so I start troubleshooting. I quickly realized the OPNsense VM shell can ping external domain names, but any internal clients couldn't resolve external names. I upgraded the VM to 23.1.4 in hopes it would solve the issue, but it did not. I ended up restoring a VM backup to a known working state from 2.5 weeks ago and clients still couldn't resolve external names.
I then disabled Unbound and enabled Dnsmasq. Clients started resolving correctly.
Why would 22.7.x and 23.1.x both have issues with internal clients resolving external names but as soon as I restored back to 22.7.x and then switched to Dnsmasq it started working? Before moving to Dnsmasq I did check the logs and found nothing out of the ordinary for Unbound.
I see the current config as a workaround and not a fix. Any ideas?
Thanks!!!
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
English Forums
»
General Discussion
»
Unbound stopped resolving