diff options
| author | Yousong Zhou <yszhou4tech@gmail.com> | 2019-02-18 14:11:19 +0000 |
|---|---|---|
| committer | Yousong Zhou <yszhou4tech@gmail.com> | 2019-02-19 13:06:06 +0000 |
| commit | ec2a2a2aea1ada65f050d74a064e74466bbe4e8d (patch) | |
| tree | c01b8155634a851d811af3057282cdb397932d0e /target/linux | |
| parent | d4c999bb891725b71ae38416cc6d5cfa99938ae4 (diff) | |
| download | upstream-ec2a2a2aea1ada65f050d74a064e74466bbe4e8d.tar.gz upstream-ec2a2a2aea1ada65f050d74a064e74466bbe4e8d.tar.bz2 upstream-ec2a2a2aea1ada65f050d74a064e74466bbe4e8d.zip | |
dnsmasq: allow using dnsmasq as the sole resolver
Currently it seems impossible to configure /etc/config/dhcp to achieve
the following use case
- run dnsmasq with no-resolv
- re-generate /etc/resolv.conf with "nameserver 127.0.0.1"
Before this change, we have to set resolvfile to /tmp/resolv.conf.auto
to achive the 2nd effect above, but setting resolvfile requires noresolv
being false.
A new boolean option "localuse" is added to indicate that we intend to
use dnsmasq as the local dns resolver. It's false by default and to
align with old behaviour it will be true automatically if resolvfile is
set to /tmp/resolv.conf.auto
Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
Acked-by: Hans Dedecker <dedeckeh@gmail.com>
Diffstat (limited to 'target/linux')
0 files changed, 0 insertions, 0 deletions