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
Software versions of OpenWrt/LEDE release, packages, etc. --> OpenWRT 21.02.1, package dnsmasq-full 2.85-8
Steps to reproduce
After installing OpenWRT 21.02.1 and replacing shipped dnsmasq package with dnsmasq-full, there is an issue, that local DNS doesn't work and no name resolution for LAN devices is possible. As a consequnce TLS encryption can't no longer be used correctly (without certificate warnings). I'm using static IP addresses and host names using Luci menu Network - Hostnames. All worked very well with many former OpenWRT versions until upgrading 21.02.1. I did several attempts and the problem is reproducable.
Message in syslog:
dnsmasq: daemon.err dnsmasq[6363]: failed to load names from /tmp/hosts/dhcp.cfg01411c: Permission denied
Workaround:
There is on old bug report for OpenWRT/LEDE 19.0.7 [https://bugs.openwrt.org/index.php?do=details&task_id=3090], where the same or at least a similar problem seems to be reported. The workaround described (adding chmod in /init.d/dnsmasq) solved this issue at my site.
The text was updated successfully, but these errors were encountered:
beko136:
After installing OpenWRT 21.02.1 and replacing shipped dnsmasq package with dnsmasq-full, there is an issue, that local DNS doesn't work and no name resolution for LAN devices is possible. As a consequnce TLS encryption can't no longer be used correctly (without certificate warnings). I'm using static IP addresses and host names using Luci menu Network - Hostnames. All worked very well with many former OpenWRT versions until upgrading 21.02.1. I did several attempts and the problem is reproducable.
Message in syslog:
dnsmasq: daemon.err dnsmasq[6363]: failed to load names from /tmp/hosts/dhcp.cfg01411c: Permission denied
Workaround:
There is on old bug report for OpenWRT/LEDE 19.0.7 [https://bugs.openwrt.org/index.php?do=details&task_id=3090], where the same or at least a similar problem seems to be reported. The workaround described (adding chmod in /init.d/dnsmasq) solved this issue at my site.
The text was updated successfully, but these errors were encountered: