Relative names with dots are now allowed if the dots are escaped

[nsc-5.git] / cf.dist / domains

diff --git a/cf.dist/domains b/cf.dist/domains
index b8974700087ca933c3e285a46892cd2e074a1041..4ec0d214bfc19694a43d8dbd608a7c9a885def92 100644 (file)
--- a/cf.dist/domains
+++ b/cf.dist/domains
@@ -1,7 +1,7 @@
 ; An example domain table for the NSC
 
 ; An example domain table for the NSC
 

-; Hints how to find root servers
-ROOTHINT()
+; 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)
 
 ; Various mandatory things required by RFC 1912, section 4.1
 PRIMARY(localhost)


@@ -31,7 +31,10 @@ BLACKHOLE(REV(192.168))
 
 ; A pretty normal example domain (we act as a primary nameserver for it)
 
 
 ; A pretty normal example domain (we act as a primary nameserver for it)
 

+DNSSEC(`                       ; DNSSEC

 PRIMARY(example.com)
 PRIMARY(example.com)

+DSFOR(a.example.com)           ; DNSSEC
+')                             ; DNSSEC

 
 ; It also has a couple of sub-domains and one of them resides on another server
 
 
 ; It also has a couple of sub-domains and one of them resides on another server
 


@@ -52,8 +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.
 
 ; 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

 REVERSE(10.0.0, example.com, a.example.com)
 REVERSE(10.1.0, example.com, a.example.com, ip6.example.com)
 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
 
 
 ; You can even have reverse zones for larger networks