Operation Manual

Example 23.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 le 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 deni-
tion can be left as is.
le example.com.zone or le “slave/example.net.zone”;
This entry species the le where zone data for the domain is located. This le is
not required for a slave, because this data is pulleds from another name server. To
differentiate master and slave les, use the directory slave for the slave les.
masters { server-ip-address; };
This entry is only needed for slave zones. It species from which name server the
zone le 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
entry, zone updates are not allowed at all. The above entry achieves the same be-
cause ! * effectively bans any such activity.
390 Reference