Difference between revisions of "Setting up unbound DNS server"

From Alpine Linux
Jump to: navigation, search
m (link)
(Configure)
Line 8: Line 8:
 
= Configure =
 
= Configure =
  
The following configuration is an example of a caching name server (in a production server, it's recommended to adjust the access-control parameter to limit to your network).
+
The following configuration is an example of a caching name server (in a production server, it's recommended to adjust the access-control parameter to limit to your network).  The forward-zone section will forward all DNS queries to the specified servers.
 
* /etc/unbound/unbound.conf
 
* /etc/unbound/unbound.conf
 
<pre>
 
<pre>
Line 23: Line 23:
 
remote-control:
 
remote-control:
 
         control-enable: no
 
         control-enable: no
</pre>
+
forward-zone:      name: "."
 +
# Level3 Verizon
 +
        forward-addr: 4.4.4.4
 +
        forward-addr: 4.2.2.4</pre>
  
 
= Set auto-start, start and test the daemon =
 
= Set auto-start, start and test the daemon =

Revision as of 21:33, 9 November 2013

Unbound is a validating, recursive, and caching DNS resolver that supports DNSSEC.

Install

Install the package:

apk add unbound

Configure

The following configuration is an example of a caching name server (in a production server, it's recommended to adjust the access-control parameter to limit to your network). The forward-zone section will forward all DNS queries to the specified servers.

  • /etc/unbound/unbound.conf
server:
        verbosity: 1
        interface: 10.0.0.1
        do-ip4: yes
        do-ip6: no
        do-udp: yes
        do-tcp: yes
        do-daemonize: yes
        access-control: 0.0.0.0/0 allow
python:
remote-control:
        control-enable: no
forward-zone:      name: "."
# Level3 Verizon
        forward-addr: 4.4.4.4
        forward-addr: 4.2.2.4

Set auto-start, start and test the daemon

Set to auto-start then start unbound:

rc-update add unbound /etc/init.d/unbound start

Test:

dig nl.alpinelinux.org @10.0.0.1