Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00) (30216-90269)

Chapter 10 263
Technical Articles
DNS BIND/iX and Syslog/iX
Refresh The refresh field specifies the time interval that must
elapse between each poll of the primary by the
secondary name server (here 36,000 seconds or 10
hours). If the “serial number” has been updated on the
primary server, the secondary name-server assumes its
data is stale and requests updated information as a
“zone transfer.”
Retry If the secondary fails to reach the primary name-server
after the refresh period, it starts trying to connect every
retry seconds, here 3600 seconds or 1 hour.
Retry Expire If the secondary fails to contact the primary
name-server for expire seconds, the secondary expires
its data. Expiring the data means the secondary stops
giving out answers about the data because the data are
too old to be useful.
Minimum The minimum time-to-live value, which specifies how
long other servers should cache data from the
name-server, here 36,000 seconds or 10 hours.
Sample Configuration Unit for a Slave Zone
zone “41.10.15.IN-ADDR.ARPA” {
type slave;
file “db.15.10.41”;
masters {
15.70.188.45;
};
}
The IP address of the server that is primary for that domain is specified
in the masters { } section of the configuration unit. There could be more
than one master for a given zone.
When the name-server comes up, looking at this configuration, it makes
a connection with the name-server running on 15.70.188.45 and does a
zone transfer, if it is required. It makes a local copy of this file too.
Configuration Migration
The configuration file in BIND/iX 8.1.1 version is called “named.conf”
which has a completely new syntax. The configuration file in BIND 4.x
version was called “named.boot.”
The migration utility “named-bootconf.pl” is available with DNS
BIND/iX and can be used to convert 4.x of named.boot file to 8.1.1
version of named.conf file. The utility “named-bootconf.pl” resides in
/BIND/PUB/bin directory.