Since the trunk builds of openwrt don't do HTTPS out of the box, I always have to run "opkg update" against the HTTP version of the openwrt package repo initially after installing a new trunk build, to download the requisite pieces for HTTPS.
Lately, "opkg update" fails frequently over HTTP on my openwrt router, even though wget the same HTTP links on a regular LAN host works fine. I have tracked this down to /etc/resolv.conf having "nameserver 127.0.0.1". It appears that dnsmasq is no longer answering DNS queries by default in the latest trunk builds, even though I've continued to use my trunk upgrade routines. I have not tracked down what and how to overcome that.
In the meantime, as a workaround, I try to temporarily replace "nameserver 127.0.0.1" in /etc/resolv.conf with "nameserver some.public.name.server". As the thread title makes clear, I find something is repeatedly resetting "nameserver some.public.name.server" back to "nameserver 127.0.0.1". So I have to open a second SSH session and repeatedly manually replace "nameserver 127.0.0.1" with "nameserver some.public.name.server" in /etc/resolv.conf, until "opkg update" finishes against the HTTP links.
So the most simplistic question is: What mechanism is regularly resetting /etc/resolv.conf, and how to make it stop, at least temporarily, for my purpose above?
Then, why is dnsmasq no longer acting as the name resolver on localhost by default? Is this a known behavior change?