一、前言
因公司的hadoop集群需要域名反向解析，之前的绑定hosts已经不能满足业务需求了，所以就折腾简单的搭建个域名系统，之前在centos5.6下搭过，有点小不一样，记录过程如下：
二、安装配置
1、安装：1
yum install -y bind bind-chroot ypbind bind-utils
2、配置：
A、撰写主配置文件
vi /etc/named.confoptions {listen-on port 53 { any; };listen-on-v6 port 53 { ::1; };directory?????? “/data/named”;dump-file?????? “/data/named/data/cache_dump.db”;statistics-file “/data/named/data/named_stats.txt”;memstatistics-file “/data/named/data/named_mem_stats.txt”;allow-query???? { any; };recursion yes;dnssec-enable yes;dnssec-validation yes;dnssec-lookaside auto;/* Path to ISC DLV key */#?????? bindkeys-file “/etc/named.iscdlv.key”;#?????? managed-keys-directory “/data/named/dynamic”;};logging {channel default_debug {file “data/query.log”;severity dynamic;};};zone “.” IN {type hint;file “named.ca”;};include “/etc/named.rfc1912.zones”;zone “navy.com” {? ##定义正向区域type master;file “/etc/named/navy.com”; ##正向区域配置文件};zone “2.10.10.in-addr.arpa” {? ##定义反向区域type master;file “/etc/named/navy.com.arpa”; ##反向区域配置文件};
B、撰写正向区域的配置文件
vi /etc/named/navy.com$TTL?? 86400@?????? IN????? SOA???? www.navy.com. root.navy.com. ( ; 开始设定内容2013060505????? ; 序号/版本号，主要用于主从同步，值大则会更新8H????????????? ; 备用DNS服务器主动更新时间间隔2H????????????? ; 备用服务器更新失败后，重试时间4W????????????? ; 超时时间，超时后备用服务器不再尝试连接主服务器1D)???????????? ; 即TTL，当无TTL设置时取此值;@?????? IN????? NS????????????? www.navy.com.www???? IN????? A?????????????? 10.10.2.201
C、撰写反向区域的配置文件
vi /etc/named/navy.com.arpa$TTL?? 86400@?????? IN????? SOA???? 2.10.10.in-addr.arpa. root.navy.com. ( ; 开始设定内容2013060505????? ; 序号/版本号，主要用于主从同步，值大则会更新8H????????????? ; 备用DNS服务器主动更新时间间隔2H????????????? ; 备用服务器更新失败后，重试时间4W????????????? ; 超时时间，超时后备用服务器不再尝试连接主服务器1D)???????????? ; 即TTL，当无TTL设置时取此值;@?????? IN????? NS????????????? www.navy.com.201???? IN????? PTR???????????? www.navy.com.
PS：这里需要注意的是IP段是倒着写的，比如上面的2.10.10意思就是10.10.2.0段
3、复制文件、权限、启动服务
mkdir /data/namedcp -r /var/named/* /data/named/chmod 777 /var/run/named/ -Rchown root:root /data/named/ -Rrndc-confgen -r /dev/urandom -a #不执行启动会报错named -c /etc/named.conf 服务启动
4、测试
root@yw-0-0 ~]# dig @10.10.2.201 www.navy.com; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.4 <<>> @10.10.2.201 www.navy.com; (1 server found);; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4473;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0;; QUESTION SECTION:;www.navy.com.????????????????? IN????? A;; ANSWER SECTION:www.navy.com.?????????? 86400?? IN????? A?????? 10.10.2.201;; AUTHORITY SECTION:navy.com.?????????????? 86400?? IN????? NS????? www.navy.com.;; Query time: 0 msec;; SERVER: 10.10.2.201#53(10.10.2.201);; WHEN: Thu Oct 17 18:11:24 2013;; MSG SIZE? rcvd: 60[root@yw-0-0 ~]# dig @10.10.2.201 201.2.10.10.in-addr.arpa ptr; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.4 <<>> @10.10.2.201 201.2.10.10.in-addr.arpa ptr; (1 server found);; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52197;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1;; QUESTION SECTION:;201.2.10.10.in-addr.arpa.????? IN????? PTR;; ANSWER SECTION:201.2.10.10.in-addr.arpa. 86400 IN????? PTR???? www.navy.com.;; AUTHORITY SECTION:2.10.10.in-addr.arpa.?? 86400?? IN????? NS????? www.navy.com.;; ADDITIONAL SECTION:www.navy.com.?????????? 86400?? IN????? A?????? 10.10.2.201;; Query time: 0 msec;; SERVER: 10.10.2.201#53(10.10.2.201);; WHEN: Thu Oct 17 18:11:33 2013;; MSG SIZE? rcvd: 98
