BIND 9.8 安装与配置指南

需积分: 9 132 浏览量更新于2024-07-21 收藏 1.22MB PDF 举报

"bind9.8管理员手册是一份全面介绍Berkeley Internet Name Domain (BIND) 9.8版本的官方文档。BIND是一款广泛应用于多种操作系统的域名服务器软件，旨在管理和解析互联网域名。该手册详细阐述了安装和维护BIND 9.8服务器的基本信息。手册首先介绍了文档的范围，涵盖了BIND 9.8.8的具体版本，并强调了版权归属。用户可以根据ISC（Internet Systems Consortium）的许可协议无限制地使用、复制、修改或分发该软件，但必须确保在所有副本中保留原始的版权通知和许可声明。手册明确指出，软件提供“按现状”使用，不承担任何明示或暗示的保证，包括适销性和适合特定用途，且不应对因使用或软件性能导致的任何直接、间接或附带损失承担责任。手册的组织结构清晰，遵循特定的编写规范，有助于读者理解和操作。内容可能包括但不限于以下几个部分： 1. 介绍：这部分会概述手册的目的，可能提到BIND在互联网基础设施中的核心作用，以及为何选择使用9.8版本。 2. 文档范围：定义了手册覆盖的主题，比如DNS（Domain Name System）基础配置、记录类型、zone管理、安全设置、性能优化等。 3. 文档结构：说明了手册章节的编排逻辑，可能包括设置指南、故障排查、配置示例、最佳实践和升级指南等。 4. 技术术语与约定：解释了在文档中使用的专业术语和符号，以便于读者理解复杂的DNS概念和技术细节。 5. 安装与配置：详细步骤指导用户如何在目标系统上安装BIND 9.8，以及如何配置基本的DNS服务，如主DNS服务器、辅助DNS服务器、转发器等。 6. 高级主题：涵盖更深入的内容，如动态更新、安全策略、负载均衡、区域传输、区域授权等高级功能。 7. 维护与故障处理：提供解决常见问题的方法，包括日志分析、性能监控、错误排查等。 8. 安全和合规性：讨论如何确保BIND服务器的安全性，如何满足不同国家和行业的法规要求。 9. 升级与迁移：介绍从旧版本升级到9.8的注意事项，以及在不同版本间进行迁移的建议。 10. 参考资料和附录：列出相关的API文档、技术报告、支持资源和联系方式，以供进一步学习和查询。通过阅读和遵循这份手册，管理员能够有效地管理和优化他们的BIND 9.8域名服务器，确保其稳定高效地为网络用户提供可靠的DNS服务。"

CHAPTER 3. NAME SERVER CONFIGURATION 3.3. NAME SERVER OPERATIONS

3.3 Name Server Operations

3.3.1 Tools for Use With the Name Server Daemon

This section describes several indispensable diagnostic, administrative and monitoring tools available

to the system administrator for controlling and debugging the name server daemon.

3.3.1.1 Diagnostic Tools

The dig, host, and nslookup programs are all command line tools for manually querying name servers.

They differ in style and output format.

dig The domain information groper (dig) is the most versatile and complete of these lookup tools. It has

two modes: simple interactive mode for a single query, and batch mode which executes a query

for each in a list of several query lines. All query options are accessible from the command line.

Usage

dig [@server] domain [query-type] [query-class] [+query-option]

[-dig-option] [%comment]

The usual simple use of dig will take the form

dig @server domain query-type query-class

For more information and a list of available commands and options, see the dig man page.

host The host utility emphasizes simplicity and ease of use. By default, it converts between host names

and Internet addresses, but its functionality can be extended with the use of options.

Usage

host [-aCdlnrsTwv] [-c class] [-N ndots] [-t type] [-W timeout] [-R

retries] [-m flag] [-4] [-6] hostname [server]

For more information and a list of available commands and options, see the host man page.

nslookup nslookup has two modes: interactive and non-interactive. Interactive mode allows the user

to query name servers for information about various hosts and domains or to print a list of hosts

in a domain. Non-interactive mode is used to print just the name and requested information for a

host or domain.

Usage

nslookup [-option...] [host-to-find | - [server]]

Interactive mode is entered when no arguments are given (the default name server will be used)

or when the ﬁrst argument is a hyphen (‘-’) and the second argument is the host name or Internet

address of a name server.

Non-interactive mode is used when the name or Internet address of the host to be looked up is

given as the ﬁrst argument. The optional second argument speciﬁes the host name or address of a

name server.

Due to its arcane user interface and frequently inconsistent behavior, we do not recommend the

use of nslookup. Use dig instead.

3.3.1.2 Administrative Tools

Administrative tools play an integral part in the management of a server.

named-checkconf The named-checkconf program checks the syntax of a named.conf ﬁle.

3.3. NAME SERVER OPERATIONS CHAPTER 3. NAME SERVER CONFIGURATION

Usage

named-checkconf [-jvz] [-t directory] [filename]

named-checkzone The named-checkzone program checks a master ﬁle for syntax and consistency.

Usage

named-checkzone [-djqvD] [-c class] [-o output] [-t directory] [-w

directory] [-k (ignore|warn|fail)] [-n (ignore|warn|fail)] [-W

(ignore|warn)] zone [filename]

named-compilezone Similar to named-checkzone, but it always dumps the zone content to a speciﬁed

ﬁle (typically in a different format).

rndc The remote name daemon control (rndc) program allows the system administrator to control the

operation of a name server. Since BIND 9.2, rndc supports all the commands of the BIND 8 ndc

utility except ndc start and ndc restart, which were also not supported in ndc’s channel mode. If

you run rndc without any options it will display a usage message as follows:

Usage

rndc [-c config] [-s server] [-p port] [-y key ] command [command...]

See rndc(8) for details of the available rndc commands.

rndc requires a conﬁguration ﬁle, since all communication with the server is authenticated with

digital signatures that rely on a shared secret, and there is no way to provide that secret other than

with a conﬁguration ﬁle. The default location for the rndc conﬁguration ﬁle is /etc/rndc.conf,

but an alternate location can be speciﬁed with the -c option. If the conﬁguration ﬁle is not found,

rndc will also look in /etc/rndc.key (or whatever sysconfdir was deﬁned when the BIND

build was conﬁgured). The rndc.key ﬁle is generated by running rndc-confgen -a as described

in Section 6.2.4.

The format of the conﬁguration ﬁle is similar to that of named.conf, but limited to only four

statements, the options, key, server and include statements. These statements are what associate

the secret keys to the servers with which they are meant to be shared. The order of statements is

not signiﬁcant.

The options statement has three clauses: default-server, default-key, and default-port. default-

server takes a host name or address argument and represents the server that will be contacted if no

-s option is provided on the command line. default-key takes the name of a key as its argument,

as deﬁned by a key statement. default-port speciﬁes the port to which rndc should connect if no

port is given on the command line or in a server statement.

The key statement deﬁnes a key to be used by rndc when authenticating with named. Its syntax

is identical to the key statement in named.conf. The keyword key is followed by a key name,

which must be a valid domain name, though it need not actually be hierarchical; thus, a string like

”rndc key” is a valid name. The key statement has two clauses: algorithm and secret. While the

conﬁguration parser will accept any string as the argument to algorithm, currently only the string

”hmac-md5” has any meaning. The secret is a base-64 encoded string as speciﬁed in RFC 3548.

The server statement associates a key deﬁned using the key statement with a server. The keyword

server is followed by a host name or address. The server statement has two clauses: key and

port. The key clause speciﬁes the name of the key to be used when communicating with this

server, and the port clause can be used to specify the port rndc should connect to on the server.

A sample minimal conﬁguration ﬁle is as follows:

key rndc_key {

algorithm "hmac-md5";

secret

"c3Ryb25nIGVub3VnaCBmb3IgYSBtYW4gYnV0IG1hZGUgZm9yIGEgd29tYW4K";

};

剩余185页未读，继续阅读

hou123456

粉丝: 25
资源: 4

BIND 9.8 安装与配置指南

Bind9 中文参考手册

BIND9管理员参考手册

]bind9配置精讲 详细具体

bind9.9管理员手册

bind9管理员手册

bind9管理员手册-BIND ARM

BIND9管理员手册.rar

bind9 管理员手册（官方英文版）

bind9管理员参考手册

BIND 9管理员参考手册

最新资源

]bind9配置精讲详细具体