DOMAIN Local Data File Format for TCP/IP

Purpose

Defines the local loopback information for the named daemon on the name server host.

Description

The local data file is one of the DOMAIN data files and contains local loopback information for the name-server host. The name of the DOMAIN local data files is specified in the named boot file.

All entries in this file must be in Standard Resource Record Format. Valid resource records in the local data file are:

The records in the DOMAIN data files are called resource records. Except for comments (starting with a ; (semicolon) and continuing to the end of the line), the resource records in the data files generally follow the format of the resource records that the named daemon returns in response to queries from resolver routines.

Examples

The following examples show the various ways to use the DOMAIN local data file. In these examples, two networks are represented: abc and xyz.

Network abc consists of:

Network xyz consists of:

  1. The named.abclocal file stored on gobi.abc contains the following entries:
    ;
    ;primary reverse file for local 127 network
    ;
    @                IN     SOA     gobi.abc.  root.gobi.abc.
                                    (
                                    1.1     ;serial
                                    3600    ;refresh
                                    600     ;retry
                                    3600000;expire
                                    86400   ;minimum
                                    )
                     IN     NS      gobi.abc.
    1                IN     PTR     localhost.
  2. The named.xyzlocal file stored on kalahari.xyz contains the following entries:
    ;
    ;primary reverse file for local 127 network
    ;
    @                IN     SOA     kalahari.xyz. root.kalahari.xyz.
                                    (
                                    1.1     ;serial
                                    3600    ;refresh
                                    600     ;retry
                                    3600000;expire
                                    86400   ;minimum
                                    )
                     IN     NS      kalahari.xyz.
    1                IN     PTR     localhost.
  3. The named.seclocal file stored on sandy contains the following entries:
    ;
    ;primary reverse file for local 127 network
    ;
    @                IN     SOA     sandy.abc.  root.sandy.abc. 
                                    (
                                    1.1     ;serial
                                    3600    ;refresh
                                    600     ;retry
                                    3600000;expire
                                    86400   ;minimum
                                    )
                     IN     NS      sandy.abc.
    1                IN     PTR     localhost.
  4. The named.calocal file stored on sahara.xyz contains the following entries:
    ;
    ;primary reverse file for local 127 network
    ;
    @                IN     SOA     sahara.xyz.  root.sahara.xyz. 
                                    (
                                    1.1   ;serial
                                    3600   ;refresh
                                    600   ;retry
                                    3600000;expire
                                    86400   ;minimum
                                    )
                     IN     NS      sahara.xyz.
    1                IN     PTR     localhost.

Files

Item Description
/etc/named.conf Defines how the named daemon initializes the DOMAIN name-server file.
/usr/samples/tcpip/named.conf Sample named.conf file, which also contains directions for its use.
/usr/samples/tcpip/named.data Sample named.data file, which also contains directions for its use.