hosts_to_na.1m (2010 09)

h
hosts_to_named(1M) hosts_to_named(1M)
(BIND 9.3)
Pointer (PTR) records are created for mapping IPv6 addresses to host names. The IPv6 PTR records are
placed in db.IP6.ARPA, if the -ARPA
option is specified; otherwise, they are placed in db.IP6.INT.
Mail exchanger (MX) records are created unless the
-M option is used. The default MX record has a
weight of 10 with the host itself as its mail exchanger. No default MX record is created for a host if
[no
smtp] is in the comment section of that line in the host table. MX records for each mail hub declared
with the -m option are added for each host even if
[no smtp] is in the comment section.
Well-known services (WKS) records are created for each host that handles SMTP mail (does not have
[no
smtp]
) if the -w option is used. The only service listed is SMTP.
Text (TXT) records are created for comments associated with hosts in the host table if the
-t option is
used. The comments do not include
[no smtp]
.
For each domain, a start-of-authority (SOA) record is created. The SOA record requires two domain
names: the host that the data is created on and the electronic mail address of the person responsible. The
-h and -u options influence the names. In addition, the SOA record requires 5 values: a serial number,
a refresh time, a retry time, an expire time, and a minimum ttl (time to live). The first time the data is
created, the serial number is set to 1, the refresh time is set to 3 hours, the retry time is set to 1 hour, the
expire time is set to 1 week, and the minimum ttl is set to 1 day. The
-o option changes these values
except for the serial number. Each subsequent time
hosts_to_named is run, the serial number is
incremented. If other fields in the SOA record are modified, the changed values are retained.
If there are files named
spcl.DOMAIN or spcl.NET in the current directory, $INCLUDE
directives
are added to the corresponding
db.DOMAIN or db.NET file for the spcl file. In this way, special data
can be added to the data generated by
hosts_to_named
.
The first time
hosts_to_named
is run, it creates a default boot file for a primary name server. Each
subsequent time
hosts_to_named is run, the boot file is updated if necessary. New entries are made
in the boot file for any additional networks or domains not already in the boot file. No entries are deleted
from the boot file.
The boot file for a caching-only server,
boot.cacheonly
(if bind is version 4.x) or conf.cacheonly
(if bind is version 8.x or 9.x), is created if it does not exist. The boot files for secondary servers,
(boot.sec.save or conf.sec.save
) and (boot.sec or conf.sec), are created if the -z or -Z
options are used. The boot files for secondary servers are created new each time from the primary server
boot file so that they are equivalent.
EXAMPLES
1. Create name server data for networks 15.19.8 and 15.19.9 in
div.inc.com.
$ hosts_to_named -d div.inc.com -n 15.19.8 -n 15.19.9
2. Create name server data for networks 15.19.8 and 15.19.9 in
div.inc.com. Ignore aliases in the
host table and include two mail hubs:
aaa.div.inc.com
and bbb.mkt.inc.com. Read all of
the options from a file.
$ hosts_to_named -f option_file
option_file contains the following lines:
-d div.inc.com
-n 15.19.8 -n 15.19.9
-m 20:aaa
-m 30:bbb.mkt.inc.com
-A
3. Network 15.19.15 has hosts in the xx.inc.com domain and the div.inc.com domain. Create
name server data for xx.inc.com. Create only pointer (PTR) data for hosts in div.inc.com on
network 15.19.15 (this requires the hosts in div.inc.com to have the canonical name or an alias
of the form x.div.inc.com).
$ hosts_to_named -d xx.inc.com -n 15.19.15 -p div.inc.com
4. Create name server data for network 15.19.8 in div.inc.com. Include div.inc.com data from
network 15.19.15 but do not create pointer (PTR) data for 15.19.15 since that is being handled by
the xx.inc.com server.
$ hosts_to_named -d div.inc.com -n 15.19.8 -a 15.19.15
4 Hewlett-Packard Company − 4 − HP-UX 11i Version 3: September 2010