Difuse/packages
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

stubby: add reload_config to documentation

Browse source 
Signed-off-by: Jonathan G. Underwood <jonathan.underwood@gmail.com>
This commit is contained in:
Jonathan G. Underwood 2018-10-27 18:28:29 +01:00
parent aa8380721b
commit 709a736043
1 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
net/stubby/files/README.md
View file

@ -1,3 +1,4 @@
# Stubby for OpenWRT # Stubby for OpenWRT
## Stubby Description ## Stubby Description
@ -86,7 +87,7 @@ command line:
uci add_list dhcp.@dnsmasq[-1].server='127.0.0.1#5453' uci add_list dhcp.@dnsmasq[-1].server='127.0.0.1#5453'
uci dhcp.@dnsmasq[-1].noresolv=1 uci dhcp.@dnsmasq[-1].noresolv=1
uci commit uci commit && reload_config
The same outcome can be achieved in the LUCI web interface as follows: The same outcome can be achieved in the LUCI web interface as follows:
@ -114,7 +115,7 @@ loopback address for both the `wan` and `wan6` interfaces in the
uci set network.wan.dns='127.0.0.1' uci set network.wan.dns='127.0.0.1'
uci set network.wan6.peerdns='0' uci set network.wan6.peerdns='0'
uci set network.wan6.dns='0::1' uci set network.wan6.dns='0::1'
uci commit uci commit && reload_config
The same outcome can also be achieved using the LUCI web interface as follows: The same outcome can also be achieved using the LUCI web interface as follows:
@ -156,7 +157,7 @@ configuration option `dnssec_return_status` to `'1'` in `/etc/config/stubby`,
which can be done by editing the file directly or by executing the commands: which can be done by editing the file directly or by executing the commands:
uci set stubby.global.dnssec_return_status=1 uci set stubby.global.dnssec_return_status=1
uci commit uci commit && reload_config
With stubby performing DNSSEC validation, dnsmasq needs to be configured to With stubby performing DNSSEC validation, dnsmasq needs to be configured to
proxy the DNSSEC data to clients. This requires setting the option `proxydnssec` proxy the DNSSEC data to clients. This requires setting the option `proxydnssec`
@ -164,7 +165,7 @@ to 1 in the dnsmasq configuration in `/etc/config/dhcp`. That can be achieved by
the following commands: the following commands:
uci set dhcp.@dnsmasq[-1].proxydnssec=1 uci set dhcp.@dnsmasq[-1].proxydnssec=1
uci commit uci commit && reload_config
#### DNSSEC by dnsmasq #### DNSSEC by dnsmasq
@ -176,7 +177,7 @@ commands:
uci set dhcp.@dnsmasq[-1].dnssec=1 uci set dhcp.@dnsmasq[-1].dnssec=1
uci set dhcp.@dnsmasq[-1].dnsseccheckunsigned=1 uci set dhcp.@dnsmasq[-1].dnsseccheckunsigned=1
uci commit uci commit && reload_config
The same options can be set in the LUCI web interface as follows: The same options can be set in the LUCI web interface as follows: