Implemented ZONE_OPTIONS and released as 3.0.

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

diff --git a/cf.dist/domains b/cf.dist/domains
index fd7afccd83e331b8ef10fc691db4955c781768f7..f222df9d170868f7c51895d17d11492fe7863947 100644 (file)
--- a/cf.dist/domains
+++ b/cf.dist/domains
@@ -15,6 +15,17 @@ PRIMARY(example.com)
 PRIMARY(a.example.com)
 SECONDARY(b.example.com, 10.0.0.1)
 
+; Yet another subdomain residing on another server, but this time with
+; access restricted to the internal network. The closing quote after the
+; options has to be on a separate line, because semicolon is a comment character.
+
+ZONE_OPTIONS(`allow-query { 127.0.0.0/8; 10.0.0.0/8; };
+       allow-recursion { 127.0.0.0/8; 10.0.0.0/8; };
+       allow-transfer { 127.0.0.0/8; 10.0.0.0/8; };
+')
+SECONDARY(priv.example.com, 10.10.10.1)
+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.
 
@@ -37,7 +48,9 @@ REVERSE(10.2, a.example.com)
 SECONDARY(REV(10.1.0.128/25), 10.1.0.2)
 
 ; And vice versa: we are delegated 10.3.0.64/26, so we want to create
-; the corresponding subdomain.
+; the corresponding subdomain. The "/" in domain name gets automatically
+; translated to "@" when forming a file name, so you will find the corresponding
+; config file in cf/64@26.0.3.10.
 
 REVERSE(10.3.0.64/26, a.example.com)