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

FS#2553 - dns name resolution with dnsmasq does not work after reboot #8378

Closed
openwrt-bot opened this issue Oct 14, 2019 · 0 comments
Closed
Labels

Comments

@openwrt-bot
Copy link

acu:

I've got a bunch of GL-MT300A devices suffering from this issue. They are configured as simple openvpn gateway behind a DSL router. There is no WIFI active, no WAN port, just a LAN interface and openvpn. Dnsmasq is used only for name resolution, and not for DHCP.

After upgrading the device from LEDE 17.01 to OpenWrt 18.06.4 r7808-ef686b7292 (latest stable version according to the website) DNS resolution failes after a reboot of the system.

Even though dnsmasq is up and running (ps shows the deamon, and netstat -tulpen shows the deamon listing to port 53 as it should be) name resolution is not working, preventing openvpn to find its servers.

After restarting dnsmasq (/etc/init.d/dnsmasq restart) name resolution starts to work as expected.

I noticed that /tmp/etc/dnsmasq.conf differes between the reboot of the router and the restart of dnsmasq.
The following line appears in the config file after restarting dnsmasq manually:

no-dhcp-interface=br-lan

Adding /etc/init.d/dnsmasq restart to /etc/rc.local seems to be a workaround for the moment.

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

No branches or pull requests

1 participant