From: Martin Mares <mj@ucw.cz>
Date: Wed, 30 Jan 2019 13:36:34 +0000 (+0100)
Subject: Show how to use example config without DNSSEC
X-Git-Tag: v5.1~14^2
X-Git-Url: http://mj.ucw.cz/gitweb/?a=commitdiff_plain;ds=sidebyside;h=25e78a5e4d9efddd909952300478057b64cb88cd;p=nsc-5.git

Show how to use example config without DNSSEC
---

diff --git a/cf.dist/domains b/cf.dist/domains
index 0cd2dcc..4ec0d21 100644
--- a/cf.dist/domains
+++ b/cf.dist/domains
@@ -1,5 +1,8 @@
 ; An example domain table for the NSC
 
+; If you do not want to use DNSSEC, please remove the lines
+; commented with "; DNSSEC".
+
 ; Various mandatory things required by RFC 1912, section 4.1
 PRIMARY(localhost)
 REVERSE(127.0.0, localhost)
@@ -28,10 +31,10 @@ BLACKHOLE(REV(192.168))
 
 ; A pretty normal example domain (we act as a primary nameserver for it)
 
-DNSSEC(`
+DNSSEC(`			; DNSSEC
 PRIMARY(example.com)
-DSFOR(a.example.com)
-')
+DSFOR(a.example.com)		; DNSSEC
+')				; DNSSEC
 
 ; It also has a couple of sub-domains and one of them resides on another server
 
@@ -52,10 +55,10 @@ ZONE_OPTIONS()
 ; Here are reverse delegations for two networks. NSC automatically creates
 ; the PTR records from A records in all mentioned zones. See cf/{0,1}.0.10.
 
-DNSSEC(`
+DNSSEC(`			; DNSSEC
 REVERSE(10.0.0, example.com, a.example.com)
 REVERSE(10.1.0, example.com, a.example.com, ip6.example.com)
-')
+')				; DNSSEC
 
 ; You can even have reverse zones for larger networks