Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 463 — #489
i
i
i
i
i
i
i
i
21
Linux in the Network
After zone, specify the name of the domain to administer, my-domain.de,
followed by in and a block of relevant options enclosed in curly braces,
as shown in Example 21.13 on the preceding page. To define a slave zone,
switch the 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 Example 21.14.
Example 21.14: Zone Entry for other-domain.de
zone "other-domain.de" in {
type slave;
file "slave/other-domain.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 definition can be left as is.
file my-domain.zone or file “slave/other-domain.zone”;
This entry specifies the file where zone data for the domain is located.
This file is not required for a slave, as this data is fetched from
another name server. To differentiate master and slave files, use the
directory slave for the slave files.
masters 10.0.0.1; ; 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 desir-
able for security reasons. Without this entry, zone updates are not al-
lowed at all. The above entry achieves the same because ! * effec-
tively bans any such activity.
463
SUSE LINUX Enterprise Server