Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX IP Address and Client Management Administrator’s Guide: HP-UX 11i v2, HP-UX 11i v3 > Chapter 2 Configuring and Administering the BIND Name Service

Starting the Name Server Daemon

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The name server daemon, /usr/sbin/named, must be running on all the master, slave, and caching-only name servers. If you have configured your system to query a remote name server (that is, if you have created an /etc/resolv.conf file that directs BIND queries to a name server on another host), you need not run the named daemon on your host.

Before you start the name server daemon, ensure that syslogd is running. syslogd logs informational and error messages. For information on configuring syslogd, see the HP-UX Internet Services Administrators Guide at the URL http://www.docs.hp.com/hpux/netcom/index.html#Internet%20Services.

Follow these steps to start the name server daemon:

  1. In the /etc/rc.config.d/namesvrs file, set the NAMED environment variable to 1, as follows:

    NAMED=1
  2. Issue the following command to determine whether named is already running:

    ps -ef │ grep named
  3. If named is not running, issue the following command to start named:

    /sbin/init.d/named start

For more information, type man 1M named at the HP-UX prompt.

Verifying the Name Server

You can use nslookup to query the name server interactively by specifying either the host name or the respective IP address of the host. nslookup displays the host name and IP address of the queried host.

To check whether the name server is configured properly, perform the following steps:

  1. Start nslookup using the following command:

    /usr/bin/nslookup
  2. At the > prompt, specify the name server you want to test in the server command as follows:

    > server BIND_server_hostname
    > server indigo.div.inc.com

    The server command causes nslookup to use the host indigo.div.inc.com as the name server for all the queries.

  3. At the > prompt, type the host name for the name server to look up, as in the following example:

    > charlie

    charlie is a host in the domain div.inc.com, where indigo.div.inc.com is configured as the name server. Therefore, the following output is displayed at the > prompt:

    Name Server: indigo.div.inc.com
    Addresses: 15.19.14.100, 15.19.15.100
    
    Name: charlie.div.inc.com
    Address: 15.19.9.100
  4. In the name server’s domain (that is, div.inc.com), look up several host names and IP addresses of hosts and check whether the respective host names and IP addresses displayed are correct.

  5. At the > prompt, type the following commands to verify that your name server queries root name servers:

    > set type=ns
    .

    nslookup must display a list of all the root name servers in the db.cache file. If nslookup does not display the root name servers, see “Troubleshooting the BIND Name Server”.

  6. If you are running syslogd, you can check the error messages in the /var/adm/syslog/syslog.log file. For more information, see “Troubleshooting the BIND Name Server”.

  7. Type exit to exit from nslookup.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.