TCPIP$UCP_HELP.HLB  —  SET  CONFIGURATION  BIND
    Configures the BIND name server. Creates the BIND server
    configuration file, which holds the following information:

    o  Cluster alias or aliases

    o  Server type (primary, secondary, or forwarding)

    o  Domains to be served

    o  Location from which the BIND server gets initial information
       for lookups

    You can configure the BIND server as follows:

    o  For one or more Internet domains

    o  As one kind of BIND server (primary, secondary, or forwarding)

    o  As multiple kinds of BIND servers

    o  On TCP/IP clusters for cluster load balancing

    This command does not create a BIND 8.1 configuration. If you
    want to take full advantage of the new features available
    with the BIND 8.1 implementation, you should set up your BIND
    environment by editing the TCPIP$BIND.CONF configuration file.
    Refer to the HP TCP/IP Services for OpenVMS Management manual for
    detailed instructions.

    If you choose to configure your BIND environment with the
    SET CONFIGURATION BIND command, you must enter the command
    CONVERT/CONFIGURATION BIND before running BIND.

    Related commands: SHOW CONFIGURATION BIND,
    CONVERT /CONFIGURATION BIND

    Format

      SET CONFIGURATION [NO]BIND  [ /CACHE=options ]

                                  [ /[NO]CLUSTER=names ]

                                  [ /FORWARDERS=options ]

                                  [ /PRIMARY=options ]

                                  [ /SECONDARY=options ]

1  –  Restrictions

    Requires SYSPRV or BYPASS privilege.

2  –  Qualifiers

2.1    /CACHE

       /CACHE=([NO]DOMAIN:do,[NO]FILE:file)

    Optional. Default: None.

    Specifies the cache server for the specified domain. Do not use
    with /FORWARDERS. Use with /PRIMARY and /SECONDARY.

    The cache tells the primary or secondary server how to use hints
    to find the file. These hints let a server find a root name
    server. With this ability, the server can answer requests even
    if it does not have the information. You can use the following
    options:

    o  DOMAIN keys to a particular record within a type.

       NODOMAIN deletes the entry.

    o  FILE specifies the name of the hints file.

    If you use /CACHE with no options:

    o  DOMAIN defaults to "." ("root").

    o  FILE defaults to NAMED.CA.

2.2    /CLUSTER

       /CLUSTER=name
       /NOCLUSTER=name

    Required to configure cluster load balancing.

    Identifies the name of a TCP/IP cluster as the first step to
    setting up cluster load balancing.

    For information about the remaining procedure, refer to the HP
    TCP/IP Services for OpenVMS Management manual.

    /NOCLUSTER=name deletes the specified name as a cluster load-
    balancing host.

2.3    /FORWARDERS

       /FORWARDERS=([NO]HOST:host)

    Optional.

    Specifies the forwarding server.

    NOHOST deletes hosts.

2.4    /PRIMARY

       /PRIMARY=([NO]DOMAIN:do,[NO]FILE:file)

    Optional. Default: None.

    Specifies the primary server for the specified zone. Multiple
    primary servers are allowed if each is associated with a
    different domain.

    o  DOMAIN keys to a particular domain.

       NODOMAIN deletes the entry.

    o  FILE specifies the domain to be served.

       If you do not specify a file, the default file name is created
       from the value that you supply with the DOMAIN option.

       NOFILE specifies that no file is created.

2.5    /SECONDARY

       /SECONDARY=([NO]DOMAIN:do,[NO]FILE:file,[NO]HOST:host)

    Optional. Default: None.

    Specifies the secondary server for the specified zone. Multiple
    secondary servers are allowed if each is associated with a
    different domain.

    o  DOMAIN keys to a particular record within a type.

       NODOMAIN deletes the entry.

    o  FILE specifies the name of the boot file.

       If you do not specify a file, the default file name is created
       from the value that you supply with the DOMAIN option.

       NOFILE specifies that no file is created.

    o  HOST is a list of hosts from which the secondary server copies
       the database file.

       NOHOST deletes hosts from the host list.

3  –  Examples

    1.TCPIP> SET CONFIGURATION BIND -
      _TCPIP> /PRIMARY=(DOMAIN:RHEA.LAB.UBIRD.EDU)

      Configures the host as the primary server for domain
      RHEA.LAB.UBIRD.EDU.

    2.TCPIP> SET CONFIGURATION BIND -
      _TCPIP> /SECONDARY=(DOMAIN:JACANA.LAB.UBIRD.EDU) -
      _TCPIP> /SECONDARY=(FILE:JACANA.DB,HOST=MARSHY)

      Configures the host as a secondary server for domain
      JACANA.LAB.UBIRD.EDU and names the boot file JACANA.DB.

      Omitting the file name would default to file JACANA_LAB_UBIRD_
      EDU.DB.

    3.TCPIP> SET CONFIGURATION BIND -
      _TCPIP> /SECONDARY=(DOMAIN:0.192.IN-ADDR.ARPA,HOST:WEBBED)

      Configures the host as a secondary server for the reverse
      lookup domain for addresses that have the form 192.0.*.*.

      The boot file name defaults to 0_192_IN-ADDR_ARPA.DB and the
      host copies this file from the host WEBBED.

    4.TCPIP> SET CONFIGURATION BIND /CACHE

      Points the server to the cache file (NAMED.CA), which contains
      hints about the root name servers.
Close Help