From b49ed4eca323fab41b79657b49e5d7f6b3fdc255 Mon Sep 17 00:00:00 2001 From: dougb Date: Sat, 22 Jan 2005 21:34:10 +0000 Subject: Scot pointed out that the dynamic zone example didn't seem to "flow" with the rest of the examples, so after discussion with him and gshapiro, re-sort the examples, and add more comments to make things very obvious. Also, divide the examples between example.{com|net|org} to make things even more obvious, and use the same RFC 1918 block for all examples. Pointed out by: Scot W. Hetzel --- etc/namedb/named.conf | 28 +++++++++++++++++----------- 1 file changed, 17 insertions(+), 11 deletions(-) (limited to 'etc') diff --git a/etc/namedb/named.conf b/etc/namedb/named.conf index 94b6f3c..e6eff00 100644 --- a/etc/namedb/named.conf +++ b/etc/namedb/named.conf @@ -93,21 +93,18 @@ zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" { // NB: Don't blindly enable the examples below. :-) Use actual names // and addresses instead. -/* -zone "example.com" { - type slave; - file "slave/example.com"; - masters { - 192.168.1.1; - }; +/* An example master zone +zone "example.net" { + type master; + file "master/example.net"; }; +*/ -// An example dynamic zone +/* An example dynamic zone key "exampleorgkey" { algorithm hmac-md5; secret "sf87HJqjkqh8ac87a02lla=="; }; - zone "example.org" { type master; allow-update { @@ -115,10 +112,19 @@ zone "example.org" { }; file "dynamic/example.org"; }; +*/ -zone "0.168.192.in-addr.arpa" { +/* Examples of forward and reverse slave zones +zone "example.com" { + type slave; + file "slave/example.com"; + masters { + 192.168.1.1; + }; +}; +zone "1.168.192.in-addr.arpa" { type slave; - file "slave/0.168.192.in-addr.arpa"; + file "slave/1.168.192.in-addr.arpa"; masters { 192.168.1.1; }; -- cgit v1.1