You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A possible cause for unbound not appearing in the Startup listing page relates to ubus and the following command:
ubus call rc list
shows that unbound is not in the returned list.
In my installation, which was an upgrade from 23.05.05, the openwrt host could resolve both IPv4 and IPv6 addresses but IPv4 clients could not resolve anything via unbound. An analysis with tcpdump showed that after some seconds, openwrt would respond with an NXDOMAIN, even when the address was in the unbound cache already.
I have reverted to 23.05.05 but please let me know if any additional data is required.
The text was updated successfully, but these errors were encountered:
There are reports of unbound not appearing in the Luci Startup listing in the Forums in this thread:
https://forum.openwrt.org/t/24-10-0-unbound-issues-luci-and-ipv4/224578/1
A possible cause for unbound not appearing in the Startup listing page relates to ubus and the following command:
ubus call rc list
shows that unbound is not in the returned list.
In my installation, which was an upgrade from 23.05.05, the openwrt host could resolve both IPv4 and IPv6 addresses but IPv4 clients could not resolve anything via unbound. An analysis with tcpdump showed that after some seconds, openwrt would respond with an NXDOMAIN, even when the address was in the unbound cache already.
I have reverted to 23.05.05 but please let me know if any additional data is required.
The text was updated successfully, but these errors were encountered: