Closed SvenHz closed 1 year ago
Is it possible that you simply did an /etc/init.d/dnsmasq stop; /etc/init.d/dnsmasq disable
on your previous deployment? This would write the DHCP received DNS server directly into /etc/resolv.conf
and it would also fall in line with your LAN interface configuration, which is set to DHCP client mode, so providing an own DHCP and DNS proxy server on OpenWrt would make little sense.
Disabled service state is not propagated across upgrades / config backup, so it is entirely possible that dnsmasq simply got reenabled after upgrade.
@jow- that is it! Thank you so much. This was the missing link. Stopping and disabling dnsmasq on the new r3 installation solves the issue and indeed it was disabled on the other AP running the earlier snapshot. Case closed!
Describe the bug
Hi, I am using OpenWRT on two Asus RT-AX53U that I am using as dumb APs. I was using OpenWrt SNAPSHOT r22479 from early April 2023 before.
I have upgraded one of the APs to OpenWrt 23.05.0-rc3, r23389.
All works fine (downlink Wifi 5GHz is 20% faster -- great!) with the exception of one thing: local (reverse) name lookup of hosts on the local LAN (10.0.0.0/24) does not work anymore (other lookups work fine). DNS server is another OpenWRT box (untouched) that is my router to the Internet (config supplied by DHCP). On the April snapshot it works fine. Configuration is identical.
I can see a difference in /tmp/resolv.conf:
April snapshot
rc3
Is this expected and how can I get the old behavior back?
OpenWrt version
r23389-5deed175a5
OpenWrt target/subtarget
ramips/mt7621
Device
ASUS RT-AX53U
Image kind
Official downloaded image
Steps to reproduce
On rc3:
On April snapshot (correct behavior):
Actual behaviour
No response
Expected behaviour
No response
Additional info
No response
Diffconfig
No response
Terms