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 <hetzels@westbend.net>
This commit is contained in:
Doug Barton 2005-01-22 21:34:10 +00:00
parent bf1639ee7d
commit 259b67a528

View File

@ -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 // NB: Don't blindly enable the examples below. :-) Use actual names
// and addresses instead. // and addresses instead.
/* /* An example master zone
zone "example.com" { zone "example.net" {
type slave; type master;
file "slave/example.com"; file "master/example.net";
masters {
192.168.1.1;
};
}; };
*/
// An example dynamic zone /* An example dynamic zone
key "exampleorgkey" { key "exampleorgkey" {
algorithm hmac-md5; algorithm hmac-md5;
secret "sf87HJqjkqh8ac87a02lla=="; secret "sf87HJqjkqh8ac87a02lla==";
}; };
zone "example.org" { zone "example.org" {
type master; type master;
allow-update { allow-update {
@ -115,10 +112,19 @@ zone "example.org" {
}; };
file "dynamic/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; type slave;
file "slave/0.168.192.in-addr.arpa"; file "slave/example.com";
masters {
192.168.1.1;
};
};
zone "1.168.192.in-addr.arpa" {
type slave;
file "slave/1.168.192.in-addr.arpa";
masters { masters {
192.168.1.1; 192.168.1.1;
}; };