Install a /var/unbound/db directory, writable by the _unbound daemon,

and use it as the default location for the DNSSEC root key. Update default
config for this location.

With this, the only step required to enable DNSSEC validation is to
uncomment these default config entries and restart:

	#module-config: "validator iterator"
	#auto-trust-anchor-file: "/var/unbound/db/root.key"

There is no longer a requirement to run unbound-anchor manually to
update the root key. The rc.d script will take care of updates at boot,
and Unbound will manage the file itself at runtime.

Test with "dig test.dnssec-or-not.net txt @127.0.0.1" or similar.

1 files changed, 3 insertions, 3 deletions

diff --git a/etc/unbound.conf b/etc/unbound.conf
index 4e0e8148b4c..ecb1fd1f382 100644
--- a/etc/unbound.conf
+++ b/etc/unbound.conf
@@ -1,4 +1,4 @@
-# $OpenBSD: unbound.conf,v 1.1 2014/03/15 00:34:18 sthen Exp $
+# $OpenBSD: unbound.conf,v 1.2 2014/03/21 00:23:15 sthen Exp $
 
 server:
 	interface: 127.0.0.1
@@ -14,10 +14,10 @@ server:
 	hide-identity: yes
 	hide-version: yes
 
-	# Enable DNSSEC validation. Fetch a root key with unbound-anchor(8).
+	# Uncomment to enable DNSSEC validation.
 	#
 	#module-config: "validator iterator"
-	#auto-trust-anchor-file: "/var/unbound/etc/root.key"
+	#auto-trust-anchor-file: "/var/unbound/db/root.key"
 
 	# Serve zones authoritatively from Unbound to resolver clients.
 	# Not for external service. Note use of "nodefault" for AS112 zones,