[root@iZwz9axd7ljna1ufs5ot9sZ ~]# yum install bind bind-utils -y Last metadata expiration check: 20:34:17 ago on Sun 25 May 2025 01:48:18 AM CST. Package bind-utils-32:9.11.36-16.0.1.al8.4.x86_64 is already installed. Dependencies resolved. ================================================================================================================================================================================================================= Package Architecture Version Repository Size ================================================================================================================================================================================================================= Installing: bind x86_64 32:9.11.36-16.0.1.al8.4 alinux3-updates 2.1 M Transaction Summary ================================================================================================================================================================================================================= Install 1 Package Total download size: 2.1 M Installed size: 4.6 M Downloading Packages: bind-9.11.36-16.0.1.al8.4.x86_64.rpm 5.5 MB/s | 2.1 MB 00:00 ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 5.4 MB/s | 2.1 MB 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Running scriptlet: bind-32:9.11.36-16.0.1.al8.4.x86_64 1/1 Installing : bind-32:9.11.36-16.0.1.al8.4.x86_64 1/1 Running scriptlet: bind-32:9.11.36-16.0.1.al8.4.x86_64 1/1 Verifying : bind-32:9.11.36-16.0.1.al8.4.x86_64 1/1 Installed: bind-32:9.11.36-16.0.1.al8.4.x86_64 Complete! [root@iZwz9axd7ljna1ufs5ot9sZ ~]# systemctl start named.service [root@iZwz9axd7ljna1ufs5ot9sZ ~]# systemctl enable named.service Created symlink /etc/systemd/system/multi-user.target.wants/named.service → /usr/lib/systemd/system/named.service. [root@iZwz9axd7ljna1ufs5ot9sZ ~]# systemctl status named.service ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2025-05-25 22:22:53 CST; 11s ago Main PID: 964006 (named) Tasks: 7 (limit: 11715) Memory: 15.2M CGroup: /system.slice/named.service └─964006 /usr/sbin/named -u named -c /etc/named.conf May 25 22:22:53 iZwz9axd7ljna1ufs5ot9sZ named[964006]: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53 May 25 22:22:53 iZwz9axd7ljna1ufs5ot9sZ named[964006]: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53 May 25 22:22:53 iZwz9axd7ljna1ufs5ot9sZ named[964006]: network unreachable resolving './NS/IN': 2001:7fe::53#53 May 25 22:22:54 iZwz9axd7ljna1ufs5ot9sZ named[964006]: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53 May 25 22:22:54 iZwz9axd7ljna1ufs5ot9sZ named[964006]: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53 May 25 22:22:54 iZwz9axd7ljna1ufs5ot9sZ named[964006]: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53 May 25 22:22:54 iZwz9axd7ljna1ufs5ot9sZ named[964006]: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53 May 25 22:22:54 iZwz9axd7ljna1ufs5ot9sZ named[964006]: resolver priming query complete May 25 22:22:57 iZwz9axd7ljna1ufs5ot9sZ named[964006]: managed-keys-zone: Key 20326 for zone . acceptance timer complete: key now trusted May 25 22:22:57 iZwz9axd7ljna1ufs5ot9sZ named[964006]: managed-keys-zone: Initializing automatic trust anchor management for zone '.'; DNSKEY ID 38696 is now trusted, waiving the normal 30-day waiting period. [root@iZwz9axd7ljna1ufs5ot9sZ ~]# zone "example.com" IN { -bash: zone: command not found [root@iZwz9axd7ljna1ufs5ot9sZ ~]# type master; -bash: type: master: not found [root@iZwz9axd7ljna1ufs5ot9sZ ~]# file "/var/named/example.com.zone"; /var/named/example.com.zone: cannot open `/var/named/example.com.zone' (No such file or directory) [root@iZwz9axd7ljna1ufs5ot9sZ ~]# allow-update { none; }; -bash: syntax error near unexpected token `}' [root@iZwz9axd7ljna1ufs5ot9sZ ~]# };$TTL 86400 -bash: syntax error near unexpected token `}' [root@iZwz9axd7ljna1ufs5ot9sZ ~]# @ IN SOA ns1.example.com. admin.example.com. ( -bash: syntax error near unexpected token `(' [root@iZwz9axd7ljna1ufs5ot9sZ ~]# 2023101001 ; Serial number -bash: 2023101001: command not found -bash: Serial: command not found [root@iZwz9axd7ljna1ufs5ot9sZ ~]# 3600 ; Refresh time (seconds) -bash: syntax error near unexpected token `(' [root@iZwz9axd7ljna1ufs5ot9sZ ~]# 1800 ; Retry time (seconds) -bash: syntax error near unexpected token `(' [root@iZwz9axd7ljna1ufs5ot9sZ ~]# 604800 ; Expire time (seconds) -bash: syntax error near unexpected token `(' [root@iZwz9axd7ljna1ufs5ot9sZ ~]# 86400 ) ; Minimum TTL (seconds) -bash: syntax error near unexpected token `)' [root@iZwz9axd7ljna1ufs5ot9sZ ~]# [root@iZwz9axd7ljna1ufs5ot9sZ ~]# IN NS ns1.example.com. -bash: IN: command not found [root@iZwz9axd7ljna1ufs5ot9sZ ~]# ns1 IN A 192.168.1.10 -bash: ns1: command not found [root@iZwz9axd7ljna1ufs5ot9sZ ~]# www IN A 192.168.1.20 -bash: www: command not found [root@iZwz9axd7ljna1ufs5ot9sZ ~]# mail IN MX 10 mail.example.com. Subject: rndc reload zone "example.com" IN { type slave; masters { 192.168.1.10; }; // Master server's IP address file "/var/named/slave/example.com.zone"; }; rndc reload dig @192.168.1.10 www.example.com 哪里出问题了
时间: 2025-06-06 18:47:06 浏览: 12
### 正确配置BIND中的example.com Zone文件及解决相关错误
#### 1. 配置Zone文件
在Alinux3系统中,BIND的默认配置文件路径为`/etc/named.conf`。对于`example.com`的正向解析区(Forward Zone),需要创建对应的区域文件,并确保其格式正确无误。
以下是标准的`example.com.zone`文件内容模板[^1]:
```plaintext
$TTL 86400
@ IN SOA ns1.example.com. admin.example.com. (
2023101001 ; Serial number
3600 ; Refresh time (seconds)
1800 ; Retry time (seconds)
604800 ; Expire time (seconds)
86400 ) ; Minimum TTL (seconds)
IN NS ns1.example.com.
ns1 IN A 192.168.1.10
www IN A 192.168.1.20
mail IN MX 10 mail.example.com.
mail IN A 192.168.1.30
```
此文件应保存为`/var/named/example.com.zone`,并赋予适当的权限和所有权[^1]:
```bash
chown named:named /var/named/example.com.zone
chmod 640 /var/named/example.com.zone
```
随后,在`/etc/named.conf`中添加以下条目以引入该区域[^1]:
```plaintext
zone "example.com" IN {
type master;
file "/var/named/example.com.zone";
allow-update { none; };
};
```
---
#### 2. 检查反向解析区
如果用户还计划配置反向解析区(Reverse Zone),则需遵循相似流程。例如,针对网络范围`192.168.1.0/24`,可创建名为`93.168.192.in-addr.arpa`的反向区域文件[^2]。
以下是典型的反向区域文件内容:
```plaintext
$TTL 86400
@ IN SOA ns1.example.com. admin.example.com. (
2023101001 ; Serial number
3600 ; Refresh time (seconds)
1800 ; Retry time (seconds)
604800 ; Expire time (seconds)
86400 ) ; Minimum TTL (seconds)
IN NS ns1.example.com.
10 IN PTR ns1.example.com.
20 IN PTR www.example.com.
30 IN PTR mail.example.com.
```
将此文件存储为`/var/named/93.168.192.in-addr.arpa`,并更新`/etc/named.conf`如下:
```plaintext
zone "93.168.192.in-addr.arpa" IN {
type master;
file "/var/named/93.168.192.in-addr.arpa";
allow-update { none; };
};
```
---
#### 3. 验证配置文件语法
完成上述配置后,务必使用`named-checkconf`工具验证主配置文件是否存在语法错误:
```bash
named-checkconf /etc/named.conf
```
同时,利用`named-checkzone`检查各区域文件的有效性:
```bash
named-checkzone example.com /var/named/example.com.zone
named-checkzone 93.168.192.in-addr.arpa /var/named/93.168.192.in-addr.arpa
```
若未报告异常,则表明配置成功。
---
#### 4. 启动与调试服务
重启BIND服务使其加载最新的配置变更:
```bash
systemctl restart named.service
```
查看日志文件排查潜在问题:
```bash
tail -f /var/log/messages
journalctl -u named.service
```
尝试执行简单的DNS查询测试连接情况:
```bash
dig @localhost www.example.com
dig -x 192.168.1.20
```
---
#### 5. 解决常见错误
- 如果发现无法解析域名,请确认防火墙是否允许UDP/TCP端口53流量。
- 若报错提示找不到指定区域文件,可能是路径拼写有误或访问权限不足。
- 当串号(Serial Number)过期时,从属服务器会拒绝同步;建议每次修改后递增该字段值。
---
阅读全文
相关推荐











