DNS------主從伺服器搭建及批量解析
配置主從伺服器
主DNS伺服器： 維護所負責解析的域內解析庫的伺服器；解析庫由管理維護
從DNS伺服器：從主DNS伺服器或其它的從DNS伺服器那裡“複製”（區域傳遞）一份解析庫
主伺服器配置
[[email protected] ~]# vim /etc/named.conf
//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
// See the BIND Administrator’s Reference Manual (ARM) for details about the
// configuration located in /usr/share/doc/bind-{version}/Bv9ARM.html
options {
listen-on port 53 { 172.16.50.37; };
directory “/var/named”;
allow-transfer { 172.16.50.60; };
};
zone “baidu.com” IN {
type master;
file “baidu.com.zone”;
};
zone “50.16.172.in-addr.arpa” IN {
type master;
file “hehe.com.zone”;
};
“/etc/named.conf” 26L, 650C
[[email protected]
從伺服器配置
在實際工作環境中，對於解析任務繁重，工作負荷較大的伺服器而言，難免存在伺服器出現問題，而在網路環境中，如果因為伺服器不能提供服務，損失將會是巨大的，因此需要做一個備份可提供服務的DNS伺服器，稱為從DNS伺服器。
從伺服器只需定義區域，而無需提供解析庫檔案；
主從啟動後，解析庫檔案會自動傳送並放置於/var/named/slaves/目錄中
[[email protected]ost slaves]# vim /etc/named.conf
options {
listen-on port 53 { 172.16.50.60; };
directory “/var/named”;
};
zone “baidu.com” IN {
type slave;
file “slaves/baidu.com.zone”;
masters { 172.16.50.37; };
};
zone “50.16.172.in-addr.arpa” IN {
type slave;
file “slaves/hehe.com.zone”;
masters { 172.16.50.37; };
};
[[email protected] ~]# systemctl restart named
**從伺服器重啟後，是否產生slaves 目錄和裡面是否有主伺服器上配置的zone區域
如果產生slaves目錄，但沒有zone區域檔案，則檢查防火牆是否關閉**
正反向批量解析：
正向解析
[[email protected] ~]# vim /var/named/baidu.com.zone
<script type="math/tex" id="MathJax-Element-113">TTL 1D @ IN SOA @ admin.baidu.com. ( 0 1D 1H 1W 3H ) IN NS ns.baidu.com. IN MX 10 mail.baidu.com. ns IN A 172.16.50.37 mail IN A 172.16.50.2 www IN A 172.16.50.1 www IN A 172.16.50.3 ftp IN CNAME www </script>GENERATE 1-10
<script type="math/tex" id="MathJax-Element-114">.baidu.com. IN A 172.16.50..</script>
[[email protected] ~]# systemctl restart named
[[email protected] ~]# dig -t A 1.baidu.com @172.16.50.37
; <<>> DiG 9.9.4-RedHat-9.9.4-50.el7 <<>> -t A 1.baidu.com @172.16.50.37
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59954
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;1.baidu.com. IN A
;; ANSWER SECTION:
1.baidu.com. 86400 IN A 172.16.50.1
;; AUTHORITY SECTION:
baidu.com. 86400 IN NS ns.baidu.com.
;; ADDITIONAL SECTION:
ns.baidu.com. 86400 IN A 172.16.50.37
;; Query time: 0 msec
;; SERVER: 172.16.50.37#53(172.16.50.37)
;; WHEN: Sat Aug 04 08:17:07 EDT 2018
;; MSG SIZE rcvd: 89
反向解析:
[[email protected] ~]# vim /var/named/hehe.com.zone
<script type="math/tex" id="MathJax-Element-115">TTL 1D @ IN SOA ns.baidu.com. admin.baidu.com. ( 0 ; serial 1D ; refresh 1H ; retry 1W ; expire 3H ) ; minimum IN NS ns.baidu.com. 37 IN PTR ns.baidu.com. 128 IN PTR www.baidu.com. </script>GENERATE 1-10
.baidu.com.
“/var/named/hehe.com.zone” 11L, 245C
[[email protected] ~]# systemctl restart named
[[email protected] ~]# dig -x 172.16.50.1 @172.16.50.37
; <<>> DiG 9.9.4-RedHat-9.9.4-50.el7 <<>> -x 172.16.50.1 @172.16.50.37
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55547
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;1.50.16.172.in-addr.arpa. IN PTR
;; ANSWER SECTION:
1.50.16.172.in-addr.arpa. 86400 IN PTR 1.baidu.com.
;; AUTHORITY SECTION:
50.16.172.in-addr.arpa. 86400 IN NS ns.baidu.com.
; ADDITIONAL SECTION:
ns.baidu.com. 86400 IN A 172.16.50.37
;; Query time: 0 msec
;; SERVER: 172.16.50.37#53(172.16.50.37)
;; WHEN: Sat Aug 04 08:24:00 EDT 2018
;; MSG SIZE rcvd: 111