From Fedora Project Wiki
Line 27: Line 27:
 
<pre>
 
<pre>
 
unbound-control list_forwards
 
unbound-control list_forwards
 +
</pre>
 +
 +
To check NetworkManager's view of the configuration, use:
 +
 +
<pre>
 +
nmcli connection show --active
 +
nmcli connection show --active <id/uuid>
 
</pre>
 
</pre>

Revision as of 09:28, 14 May 2014

Manual configuration via Unbound

TBD

Local zones

TBD

Global zone

TBD

Using dnssec-trigger (for testing only)

dnssec-trigger configures /etc/resolv.conf to use a local unbound instance on 127.0.0.1 and Unbound to use a secure global zone with nameservers submitted through dnssec-trigger-control or, if those aren't suitable, using public nameservers run by Fedora or the upstream project.

It also performs captive portal (hotspot) detection and temporarily changes /etc/resolv.conf to include the nameservers of the local network directly. That unfortunately breaks the local zones used with any network interfaces including those that have nothing to do with the captive portal connection.

NetworkManager integration

TBD

Debugging

Show connection zones configuration in unbound:

unbound-control list_forwards

To check NetworkManager's view of the configuration, use:

nmcli connection show --active
nmcli connection show --active <id/uuid>