@ IN SOA test.com. administrator.test.com. (
1; serial number
10800 ; refresh after 3 hours
3600; retry after 1 hour
604800; expire after 1 week
86400 
;minimum TTL of 1 day
IN NS dns.test.com.
1 IN PTR dns.test.com.
2 IN PTR num2.test.com.
dns.test.com. IN A 192.1.1.1
--end /var/named/named.rev--
NOTE: there should be one PTR record as above for each machine in the
1.1.192.in-addr.arpa domain, that is every machine whose network
number starts with 192.1.1.
DON'T FORGET THE TRAILING "."!!!
There will also need to be a /var/named/named.ca file, which should be
retrieved as described in section 3.5.
The books listed in sections 7.4 and 7.5 give a much more in depth
description of setting up a caching only name server.
3.8: How to Set Up a Secondary DNS Server
Following is a sample of how to set up a secondary DNS server. This
will be a name server which will cache records it looks up, and also
backs up records for a domain. Please note that we secondary both the
domain test.com, and a theoretical set of IP addresses for that
domain, 192.1.1.0.
--start /etc/named.boot--
;
; named.boot file for a caching only name server
;
directory /var/named
cache . named.ca
primary 0.0.127.in-addr.arpa named.local
secondary test.com 192.1.1.1 named.test
secondary 1.1.192.in-addr.arpa 192.1.1.1 named.rev
--end /etc/named.boot--
The ip address noted for the secondary lines (192.1.1.1 in this
example) should be the IP address of the machine that is primary for
the domain.
The named.ca file should be retrieved as described in section 3.5.
The named.local file should be created as described in section 3.6.
The named.test and named.rev files will automatically be created when
in.named is started up, by downloading the information from the
primary server.
Note: although this example only shows secondary lines, machines can
actually combine primary and secondary lines in arbitrary ways. For
example, a machine could primary test.com, and secondary foo.org, as a
favor to a nearby domain.