[root@localhost ~]# dnssec-keygen -a HMAC-MD5 -b  -n HOST master-slave  //-a 指定加密算法 -b指定加密长度 -n 指定类型

Kmaster-slave.++

[root@localhost ~]# ll Kmaster-slave.++.*

-rw-------.  root root   Feb  : Kmaster-slave.++.key

-rw-------.  root root  Feb  : Kmaster-slave.++.private

[root@localhost ~]# 

[root@localhost ~]# vim /var/named/chroot/etc/transfer.key

key "master-slave" {

algorithm hmac-md5;

secret "driJBeDX3zCdS2XptPG5tg==";

};

[root@localhost ~]# chown root:named /var/named/chroot/etc/transfer.key

[root@localhost ~]# ln /var/named/chroot/etc/transfer.key /etc/transfer.key

[root@localhost ~]# 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.

//

include "/etc/transfer.key";             //在主服务器中添加此条

options {

        listen-on port  { any; };

        listen-on-v6 port  { ::; };

        directory       "/var/named";

        dump-file       "/var/named/data/cache_dump.db";

        statistics-file "/var/named/data/named_stats.txt";

        memstatistics-file "/var/named/data/named_mem_stats.txt";

        allow-query     { any; };

        allow-transfer  { key master-slave; };

        /*

         - If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.

         - If you are building a RECURSIVE (caching) DNS server, you need to enable

           recursion.

         - If your recursive DNS server has a public IP address, you MUST enable access

           control to limit queries to your legitimate users. Failing to do so will

           cause your server to become part of large scale DNS amplification

           attacks. Implementing BCP38 within your network would greatly

           reduce such attack surface

        */

        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 "/var/named/dynamic";

        pid-file "/run/named/named.pid";

        session-keyfile "/run/named/session.key";

};

logging {

        channel default_debug {

                file "data/named.run";

                severity dynamic;

        };

};

zone "." IN {

        type hint;

        file "named.ca";

};

include "/etc/named.rfc1912.zones";

include "/etc/named.root.key";

[root@localhost ~]# scp /var/named/chroot/etc/transfer.key root@192.168.16.30:/var/named/chroot/etc/

The authenticity of host '192.168.16.30 (192.168.16.30)' can't be established.

ECDSA key fingerprint is e6:a7::::ce::ac::3a:b7:d1::9c::e1.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added '192.168.16.30' (ECDSA) to the list of known hosts.

root@192.168.16.30's password:

transfer.key                                                                                                                              %        .1KB/s   :    

[root@localhost ~]# chown root:named /var/named/chroot/etc/transfer.key

[root@localhost ~]# ln /var/named/chroot/etc/transfer.key /etc/transfer.key

[root@localhost slaves]# !v

vim /etc/named.conf 

options {

        listen-on port  { any; };

        listen-on-v6 port  { ::; };

        directory       "/var/named";

        dump-file       "/var/named/data/cache_dump.db";

        statistics-file "/var/named/data/named_stats.txt";

        memstatistics-file "/var/named/data/named_mem_stats.txt";

        allow-query     { any; };

        include "/etc/transfer.key";

        /*

         - If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.

         - If you are building a RECURSIVE (caching) DNS server, you need to enable

           recursion.

         - If your recursive DNS server has a public IP address, you MUST enable access

           control to limit queries to your legitimate users. Failing to do so will

           cause your server to become part of large scale DNS amplification

           attacks. Implementing BCP38 within your network would greatly

           reduce such attack surface

        */

        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 "/var/named/dynamic";

        pid-file "/run/named/named.pid";

        session-keyfile "/run/named/session.key";

};

server 192.168.16.20 {                   //"192.168.16.20"为主服务器IP地址，在从服务器中添加此条

        keys { master-slave; };

};



logging {

        channel default_debug {

                file "data/named.run";

                severity dynamic;

        };

};

zone "." IN {

        type hint;

        file "named.ca";

};

include "/etc/named.rfc1912.zones";

include "/etc/named.root.key";

[root@localhost ~]# ls /var/named/slaves/

kernel.org.zone

[root@localhost ~]# rm -rf /var/named/slaves/kernel.org.zone

[root@localhost ~]# ls /var/named/slaves/

[root@localhost ~]# systemctl restart named

[root@localhost ~]# ls /var/named/slaves/

kernel.org.zone

[root@localhost ~]#