mail this page
products | company | support | training | contact us
A zone is convenient short-hand for that part of the domain name for which we are configuring the DNS server, for example, BIND and is always an entity for which we are authoritative.
Assume we have a domain name of example.com. This is comprised of a domain-name (example) and a gTLD name (com). The zone in this case is example.com. If we we have a sub-domain which has been delegated to us called us.example.com then the zone is us.example.com.
Zones are described in zone files (sometimes called master files and normally located in /var/named) which can contain Directives used by the DNS software, for example, BIND and Resource Records which describe the characteristics of the zone and individual hosts and services within the zone. Both Directives and Resource records are a standard defined by RFC 1035 so can be read by any self-respecting DNS server software. The single exception to this is the BIND-specific $GENERATE directive. So if you think you will change DNS servers don't use $GENERATE.
example.com. IN SOA ns1.example.com. hostmaster.example.com.( 2003080800 ; se = serial number 3h ; ref = refresh 15m ; ret = update retry 3w ; ex = expiry 3h ; min = minimum ) IN NS ns1.example.com. IN NS ns2.example.com. IN MX 10 mail.anotherdomain.com. joe IN A 192.168.254.3 www IN CNAME joe
3 reverse map
4 dns types
5 install bind
8 dns records
12 bind api's
13 dns security
bits & bytes
notes & tips
This work is licensed under a Creative Commons License.
If you are happy it's OK - but your browser is giving a less than optimal experience on our site. You could, at no charge, upgrade to a W3C STANDARDS COMPLIANT browser such as Mozilla