Setting up unbound DNS server: Difference between revisions
(remove the zone data, unbound is far more useful as caching-only) |
Dubiousjim (talk | contribs) (Category:Networking) |
||
Line 32: | Line 32: | ||
Test: | Test: | ||
{{Cmd|dig nl.alpinelinux.org @10.0.0.1}} | {{Cmd|dig nl.alpinelinux.org @10.0.0.1}} | ||
[[Category:Networking]] |
Revision as of 07:15, 12 March 2012
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).
- /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
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