Created
March 11, 2021 08:00
-
-
Save hisashiyamaguchi/74167ea37167f82e3f6b8c9aa53e7e23 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
options { | |
listen-on port 53 { 127.0.0.1; any;}; | |
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"; | |
recursing-file "/var/named/data/named.recursing"; | |
secroots-file "/var/named/data/named.secroots"; | |
allow-query { localhost; any;}; | |
/* | |
- 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.root.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"; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment