HP DNS Configuration and Management Manual Abstract This manual describes how to implement Domain Name System (DNS) 9.2.3 on the NonStop Server in the HP NonStop Open System Services (OSS) environment. This manual is intended for network administrators responsible for managing DNS. Product Version DNS 9.2.3 Supported Release Version Updates (RVUs) This publication supports G06.25 and all subsequent RVUs until otherwise indicated in a new edition.
Document History Part Number Product Version 529432-001 DNS 9.2.
HP DNS Configuration and Management Manual Glossary Index What’s New in This Manual iii Manual Information iii New and Changed Information Examples Figures Tables iii About This Manual v Manual Organization v Supported RFCs v Statement for Ported Software and Related Documentation Assumptions About the Reader vii Related Manuals vii Notation Conventions vii Abbreviations xii vi 1. Quick Start I. Prepare to Start DNS 9.2.3 1-1 1. Check Assumptions Before Starting DNS 9.2.3 II. Start DNS 9.2.
3. Configuring and Managing DNS 9.2.3 (continued) Contents 3. Configuring and Managing DNS 9.2.3 (continued) Using the named-bootconf Utility to Migrate the Configuration File Using the nsupdate Tool 3-3 Using the rndc Tool 3-3 Specifying a Different resolv.conf File 3-3 Using IXFR 3-4 Performing Dynamic Updates 3-5 3-2 4. Troubleshooting Troubleshooting DNS 9.2.3 Logging in DNS 9.2.3 4-3 4-1 Glossary Index Examples Example 3-1. Example 3-2. Example 3-3. Example 3-4. Example 3-5. Example 4-1.
What’s New in This Manual Manual Information HP DNS Configuration and Management Manual Abstract This manual describes how to implement Domain Name System (DNS) 9.2.3 on the NonStop Server in the HP NonStop Open System Services (OSS) environment. This manual is intended for network administrators responsible for managing DNS. Product Version DNS 9.2.3 Supported Release Version Updates (RVUs) This publication supports G06.25 and all subsequent RVUs until otherwise indicated in a new edition.
What’s New in This Manual New and Changed Information HP DNS Configuration and Management Manual—529432-001 iv
About This Manual This manual describes how to implement Domain Name System (DNS) 9.2.3 on NonStop Server in the HP NonStop Open System Services (OSS) environment. For general information about DNS 9.2.3, see the BIND 9 Administrator Reference Manual in the NonStop Technical Library (NTL).
About This Manual Statement for Ported Software and Related Documentation updated definitions of existing query types that return Internet addresses as part of additional section processing. • • RFC 2874: DNS Extensions to Support IPv6 Address Aggregation and Renumbering • • • • • • The extensions are compatible with existing applications and, in particular, DNS implementations themselves. Changes are made to DNS to support aggregated and renumbered IPv6 addressing.
Assumptions About the Reader About This Manual TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
General Syntax Notation About This Manual This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters.
General Syntax Notation About This Manual braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis.
Notation for Messages About This Manual !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program). For example: CALL CHECKRESIZESEGMENT ( segment-id , error ) ; !i !o !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program).
Change Bar Notation About This Manual [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
Abbreviations About This Manual Abbreviations BIND Berkeley Internet Name Domain DNS Domain Name System ISC Internet Systems Consortium IXFR Incremental Zone Transfer OSS Open System Services HP DNS Configuration and Management Manual—529432-001 xii
1 Quick Start This section provides examples of preparing to start Domain Name System (DNS) 9.2.3, starting DNS 9.2.3, and stopping DNS 9.2.3.
II. Start DNS 9.2.3 Quick Start • • • • • • rndc rndc.conf db.myzone.com.in NonStop TCP/IP is running. If you plan to use IPv6 communications, verify that NonStop TCP/IPv6 is running in DUAL or INET6 mode; refer to the TCP/IPv6 Configuration and Management Manual in NTL for more information. You are the super ID (equivalent to a UNIX root user) You have the following software components to run a Name Server: • • • DNS 9.2.3 name daemon Valid configuration file (named.conf) Zone files II.
III. Stop DNS 9.2.3 Quick Start 2. Enter the following command at the prompt to stop named: /etc/dns923>kill -term process-id The above command sends the SIGTERM signal to the named process, causing the process to terminate. Note. If named is a persistent process, see Managing Persistence for the named Process on page 3-1; the kill command does not stop the named process.
III. Stop DNS 9.2.
2 Introduction to DNS 9.2.3 This section serves as a brief introduction to the Domain Name System (DNS) 9.2.3 process. For a more thorough discussion of DNS 9.2.3, see the BIND 9 Administrator Reference Manual in the NonStop Technical Library (NTL).
Introduction to DNS 9.2.3 Restrictions and Features Restrictions and Features Restrictions • To make DNS a persistent process using the NonStop Kernel Persistence Manager ($ZZKRN), you should have the G06.24 RVU installed on the system. Features • DNS Protocol Enhancements Incremental Zone Transfer (IXFR), NOTIFY, and dynamic updates are used for efficient zone transfer, reducing size and duration, and supporting the increasing amount of data being exchanged between Name Servers.
Introduction to DNS 9.2.3 nsupdate The syntax for this tool is: /etc/dns923> named-bootconf.sh < DNS 4.8.3 configuration file (input) > DNS 9.2.3 configuration file (output) Refer to Using the named-bootconf Utility to Migrate the Configuration File on page 3-2 for an example of using the named-bootconf tool. Note. “<“ and “>” are redirection operators. Refer to Using the nsupdate Tool on page 3-3. nsupdate The nsupdate tool updates DNS 9.2.
Introduction to DNS 9.2.3 • • rndc (remote name daemon control) halt: Stops the server immediately. Recent changes made through dynamic update or IXFR are not saved to the master files, but are rolled forward from the journal files when the server is restarted. status: Displays the status of the server. Refer to Using the rndc Tool on page 3-3 for an example of using the rndc tool.
3 Configuring and Managing DNS 9.2.3 • • • • • • • • Managing Persistence for the named Process on page 3-1 Specifying a TCP/IP Process By Using a Runtime Option on page 3-2 Using the named-bootconf Utility to Migrate the Configuration File on page 3-2 Using the nsupdate Tool on page 3-3 Using the rndc Tool on page 3-3 Specifying a Different resolv.
Configuring and Managing DNS 9.2.3 Stopping the named Process as a Persistent Process Stopping the named Process as a Persistent Process 1. To stop the named process if it is configured as a persistent process (autorestart > 0), issue the SCF ABORT command to the NonStop Kernel subsystem as shown: ->abort $zzkrn.#named For more information about managing persistence, see the SCF Reference Manual for the Kernel Subsystem in NTL.
Configuring and Managing DNS 9.2.3 Using the nsupdate Tool In the example above, “<“ and “>” are redirection operators. Note. Since the manner of specifying pathnames is different in Guardian and OSS, you must ensure that the new configuration file (after conversion) contains the appropriate path of the zone files. Using the nsupdate Tool The nsupdate tool can be used to dynamically update the DNS 9.2.3 Name Server.
Configuring and Managing DNS 9.2.3 Using IXFR The new environment variable TCPIP_RESOLVER_NAME must be used for pointing to the resolv.conf file; this variable can be set either through the OSS shell prompt or through a call to the putenv() procedure in the OSS application. The following pieces of code are examples of resolving the destination host by querying the Name Server pointed at by the /etc/dns/resolv.conf file. Example 3-4. Specifying a Different resolv.
Configuring and Managing DNS 9.2.3 Performing Dynamic Updates whenever possible. If set to no (case sensitive), all transfers to the remote server are non-incremental. Performing Dynamic Updates For dynamic updates to be processed by the Name Server, specify the IP addresses of the systems from where the requests can be received. The IP addresses are specified in the configuration file under the zone entry.
Configuring and Managing DNS 9.2.
4 Troubleshooting This section provides guidelines for troubleshooting various problems you may encounter with DNS 9.2.3. This section contains the following information: • • Troubleshooting DNS 9.2.3 on page 4-1 Logging in DNS 9.2.3 on page 4-3 Troubleshooting DNS 9.2.3 In most cases, the primary cause of the process named failing to start is faulty configuration.
Troubleshooting DNS 9.2.3 Troubleshooting Example 4-1. Sample named.conf File 1 /*Sample configuration file */ 2 3 options { 4 directory "/user/dns/nameddir"; 5 pid-file "named.pid" 6 listen-on { 172.31.45.115; }; /*semicolon missing*/ 7 }; 8 9 logging { 10 channel my_syslog { 11 syslog daemon; 12 severity info; 13 } /*semicolon missing*/ 14 15 channel my_file { 16 file "log.
Logging in DNS 9.2.3 Troubleshooting As shown, the error is displayed along with date, time and line numbers (5 and 13 in this case). Logging in DNS 9.2.3 There are two main phrases in logging: • • Channels specify where the data is logged Categories specify what kind of data (queries, updates, statistics, etc.
Logging in DNS 9.2.3 Troubleshooting Figure 4-1. Logging Categories to Channels statistics category syslog channel queries category log_file channel The Name Server can be instructed to enable this feature by specifying the logging statement in the named.conf file. An example statement in the named.conf file is: Example 4-2. Logging Statement in named.conf File logging { channel my_ems { syslog daemon; severity info; }; channel my_file { file "mylog.
Logging in DNS 9.2.3 Troubleshooting • • statistics instructs the Name Server to send the statistical data to both EMS and a local file queries instructs the Name Server to send the logging data on queries to a local file only Refer to the BIND 9 Administrator Reference Manual in NTL for additional information on the logging statement, channels, and categories.
Logging in DNS 9.2.
Glossary Advanced Research Projects Agency (ARPA). An agency of the United States Department of Defense, ARPA underwrote the development of the Internet beginning in 1969. Known as ARPANET, it was designed so that, in case of war and the loss of any group of sites, remaining sites would still be able to communicate along alternate routes. No site would be critical to the operation of the network.
Internet protocol version 4 (IPv4) Glossary Internet protocol version 4 (IPv4). The most widely deployed version of the Internet protocol. IPv4 provides some basic traffic classification mechanisms with its IP Precedence/CBQ and Type of Service header fields. However, network hardware and software have not been configured to use them. Internet protocol version 6 (IPv6). An update to the Internet protocol version 4 (IPv4).
resolv.conf file. Glossary to become Internet standards, the final version of the RFC becomes the standard and no further comments or changes are permitted. Change can occur, however, through subsequent RFCs that supersede or elaborate on all or parts of previous RFCs. resolv.conf file. A file that contains details about the address of the Name Server to contact and the domain name to which it belongs. Resource Record (RR). A DNS data record. RFC. See Request for Comment (RFC). RR.
zone file Glossary HP DNS Configuration and Management Manual—529432-001 Glossary- 4
Index Numbers DNS 9.2.3 (continued) starting 1-2 stopping 1-2 troubleshooting 4-1 verifying that installed 1-1 DUAL mode 1-2 dynamic update 3-5 1886 (RFC) v 2845 (RFC) vi 2874 (RFC) vi A abbreviations xii abort command 3-2 add process command 3-1 assumptions about the reader vii F file named.conf 2-1 named.conf (logging statement in) 4-4 named.conf (sample) 4-2 resolv.conf 2-1, 3-3 B BIND 9 Administrator Reference Manual vii C I categories 4-3 channels 4-3 checking that DNS 9.2.
O Index named.conf file 2-1 notation conventions vii nsupdate 2-3, 3-3 O organization of manual v OSS subsystem 1-1 overview of DNS 2-1 P performing dynamic updates 3-5 prepare to start DNS 9.2.3 1-1 putenv() procedure 3-4 T TCPIP_RESOLVER_NAME variable 3-4 TCP/IPv6 Configuration and Management Manual 1-1, 1-2 tools 2-2 U using named-bootconf to migrate the configuration file 3-2 Z zone entry 3-5 zone file 1-2, 2-1, 3-3 R Special Characters reader assumptions vii related manuals vii resolv.
