Novell LINUX ENTERPRISE SERVER 11 - ADMINISTRATION Administration Manual page 309

After zone, specify the name of the domain to administer (example.com) followed
by in and a block of relevant options enclosed in curly braces, as shown in
ple 21.4, "Zone Entry for example.com"
type to slave and specify a name server that administers this zone as master
(which, in turn, may be a slave of another master), as shown in
Entry for example.net"
Example 21.5 Zone Entry for example.net
zone "example.net" in {
type slave;
file "slave/example.net.zone";
masters { 10.0.0.1; };
};
The zone options:
type master;
By specifying master, tell BIND that the zone is handled by the local name
server. This assumes that a zone file has been created in the correct format.
type slave;
This zone is transferred from another name server. It must be used together with
masters.
type hint;
The zone . of the hint type is used to set the root name servers. This zone defini-
tion can be left as is.
file example.com.zone or file "slave/example.net.zone";
This entry specifies the file where zone data for the domain is located. This file is
not required for a slave, because this data is pulleds from another name server. To
differentiate master and slave files, use the directory slave for the slave files.
masters { server-ip-address; };
This entry is only needed for slave zones. It specifies from which name server the
zone file should be transferred.
allow-update {! *; };
This option controls external write access, which would allow clients to make a
DNS entry—something not normally desirable for security reasons. Without this
(page 294). To define a slave zone, switch the
(page 295).
Exam-
Example 21.5, "Zone
The Domain Name System 295