僕の経験不足かもしれませんが設定を見直しましたが特におかしなところはありませんでした...
起動ではエラーが出ます
# systemctl start named Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.
systemctl status namedも実行しました。
# systemctl status named ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since 日 2021-01-10 17:21:28 JST; 4s ago Process: 30636 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE) 1月 10 17:21:28 www.newjapanserver.tokyo bash[30636]: _default/www.newjapanserver.tokyo/IN: bad zone 1月 10 17:21:28 www.newjapanserver.tokyo bash[30636]: zone localhost.localdomain/IN: loaded serial 0 1月 10 17:21:28 www.newjapanserver.tokyo bash[30636]: zone localhost/IN: loaded serial 0 1月 10 17:21:28 www.newjapanserver.tokyo bash[30636]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0 1月 10 17:21:28 www.newjapanserver.tokyo bash[30636]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0 1月 10 17:21:28 www.newjapanserver.tokyo bash[30636]: zone 0.in-addr.arpa/IN: loaded serial 0 1月 10 17:21:28 www.newjapanserver.tokyo systemd[1]: named.service: control process exited, code=exited status=1 1月 10 17:21:28 www.newjapanserver.tokyo systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). 1月 10 17:21:28 www.newjapanserver.tokyo systemd[1]: Unit named.service entered failed state. 1月 10 17:21:28 www.newjapanserver.tokyo systemd[1]: named.service failed.
起動できません。
教えていただけると幸いです。
追記
//
// 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 { 122.103.80.170; };
listen-on-v6 port 53 { none; };
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 { any; };
use-v6-udp-ports { };
/* - 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 no; 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"; rate-limit { responses-per-second 5; window 5; };
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
zone "www.newjapanserver.tokyo" IN {
type master;
file "www.newjapanserver.tokyo.zone";
};
include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";
追記2
named-checkconfやってみました
#named-checkconf /etc/named.conf //表示なし、エラーなし?
回答1件
あなたの回答
tips
プレビュー