質問編集履歴
2
named-checkconf
title
CHANGED
|
File without changes
|
body
CHANGED
|
@@ -94,4 +94,10 @@
|
|
|
94
94
|
};
|
|
95
95
|
|
|
96
96
|
include "/etc/named.rfc1912.zones";
|
|
97
|
-
include "/etc/named.root.key";
|
|
97
|
+
include "/etc/named.root.key";
|
|
98
|
+
追記2
|
|
99
|
+
named-checkconfやってみました
|
|
100
|
+
```
|
|
101
|
+
#named-checkconf /etc/named.conf
|
|
102
|
+
//表示なし、エラーなし？
|
|
103
|
+
```
|
1
named.confの追記
title
CHANGED
|
File without changes
|
body
CHANGED
|
@@ -24,4 +24,74 @@
|
|
|
24
24
|
1月 10 17:21:28 www.newjapanserver.tokyo systemd[1]: named.service failed.
|
|
25
25
|
```
|
|
26
26
|
起動できません。
|
|
27
|
-
教えていただけると幸いです。
|
|
27
|
+
教えていただけると幸いです。
|
|
28
|
+
追記
|
|
29
|
+
//
|
|
30
|
+
// named.conf
|
|
31
|
+
//
|
|
32
|
+
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
|
|
33
|
+
// server as a caching only nameserver (as a localhost DNS resolver only).
|
|
34
|
+
//
|
|
35
|
+
// See /usr/share/doc/bind*/sample/ for example named configuration files.
|
|
36
|
+
//
|
|
37
|
+
// See the BIND Administrator's Reference Manual (ARM) for details about the
|
|
38
|
+
// configuration located in /usr/share/doc/bind-{version}/Bv9ARM.html
|
|
39
|
+
|
|
40
|
+
options {
|
|
41
|
+
listen-on port 53 { 122.103.80.170; };
|
|
42
|
+
listen-on-v6 port 53 { none; };
|
|
43
|
+
directory "/var/named";
|
|
44
|
+
dump-file "/var/named/data/cache_dump.db";
|
|
45
|
+
statistics-file "/var/named/data/named_stats.txt";
|
|
46
|
+
memstatistics-file "/var/named/data/named_mem_stats.txt";
|
|
47
|
+
recursing-file "/var/named/data/named.recursing";
|
|
48
|
+
secroots-file "/var/named/data/named.secroots";
|
|
49
|
+
allow-query { any; };
|
|
50
|
+
use-v6-udp-ports { };
|
|
51
|
+
|
|
52
|
+
|
|
53
|
+
|
|
54
|
+
|
|
55
|
+
/*
|
|
56
|
+
- If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.
|
|
57
|
+
- If you are building a RECURSIVE (caching) DNS server, you need to enable
|
|
58
|
+
recursion.
|
|
59
|
+
- If your recursive DNS server has a public IP address, you MUST enable access
|
|
60
|
+
control to limit queries to your legitimate users. Failing to do so will
|
|
61
|
+
cause your server to become part of large scale DNS amplification
|
|
62
|
+
attacks. Implementing BCP38 within your network would greatly
|
|
63
|
+
reduce such attack surface
|
|
64
|
+
*/
|
|
65
|
+
recursion no;
|
|
66
|
+
|
|
67
|
+
dnssec-enable yes;
|
|
68
|
+
dnssec-validation yes;
|
|
69
|
+
|
|
70
|
+
/* Path to ISC DLV key */
|
|
71
|
+
bindkeys-file "/etc/named.root.key";
|
|
72
|
+
|
|
73
|
+
managed-keys-directory "/var/named/dynamic";
|
|
74
|
+
|
|
75
|
+
pid-file "/run/named/named.pid";
|
|
76
|
+
session-keyfile "/run/named/session.key";
|
|
77
|
+
|
|
78
|
+
rate-limit {
|
|
79
|
+
responses-per-second 5;
|
|
80
|
+
window 5;
|
|
81
|
+
};
|
|
82
|
+
};
|
|
83
|
+
|
|
84
|
+
logging {
|
|
85
|
+
channel default_debug {
|
|
86
|
+
file "data/named.run";
|
|
87
|
+
severity dynamic;
|
|
88
|
+
};
|
|
89
|
+
};
|
|
90
|
+
|
|
91
|
+
zone "www.newjapanserver.tokyo" IN {
|
|
92
|
+
type master;
|
|
93
|
+
file "www.newjapanserver.tokyo.zone";
|
|
94
|
+
};
|
|
95
|
+
|
|
96
|
+
include "/etc/named.rfc1912.zones";
|
|
97
|
+
include "/etc/named.root.key";
|