SSH to server as scotty
options {
listen-on port 53 { 127.0.0.1; 192.168.123.222;};
listen-on-v6 port 53 { ::1; };
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 { localhost; 192.168.123.0/24;10.5.5.0/24;};
/*
- 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;
/* 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";
};
zone "err" IN {
type slave;
file "/var/named/slaves/forward.errigal";
masters { 10.91.100.71; };
};
zone "100.91.10.in-addr.arpa" IN {
type slave;
file "/var/named/slaves/reverse.errigal";
masters { 10.91.100.71; };
};
zone "crc" IN {
type slave;
file "/var/named/slaves/forward.crown";
masters { 10.91.100.71; };
};
zone"30.10.in-addr.arpa" IN {
type slave;
file "/var/named/slaves/reverse.crown";
masters { 10.91.100.71; };
};
zone "ext" IN {
type slave;
file "/var/named/slaves/forward.extenet";
masters { 10.91.100.71; };
};
zone"104.214.10.in-addr.arpa" IN {
type slave;
file "/var/named/slaves/reverse.extenet";
masters { 10.91.100.71; };
};
allow-transfer { localhost; 10.5.5.50; 10.5.5.15; 192.168.123.211; 192.168.123.222; }; # Slave DNS Servers IP
has your slave ip address.