On Wed, Jan 27, 2016 at 10:00 AM, Motokazu Nakai <[email protected]> wrote:
> Hi > > I am trying to set up DNS server. but I encountered error, and enable to > set up DNS server unfortunately. > > I have done creating these files below. I checked inside files are > collect. I don't know what is wrong. > I put the error message here. > Could you please provide me some ways to solve this problem? > > <Files I created> > "vi /etc/named.conf" > "vi /var/named/individualmoto.ddns.net.lan" > "vi /var/named/1.168.192.in-addr.arpa.db" > "vi /var/named/individualmoto.ddns.net.wan" > "vi /var/named/217.194.125.in-addr.arpa.db" > > And I hit "systemctl start named.service" > > Then I received this message below. > "Job for named.service failed. See 'systemctl status named.service' and > 'journalctl -xn' for details." > > To find what is wrong I hit 'systemctl status named.service' and > 'journalctl -xn' > > The result for 'systemctl status named.service' was this. > > systemctl status named.service > named.service - Berkeley Internet Name Domain (DNS) > Loaded: loaded (/usr/lib/systemd/system/named.service; disabled) > Active: failed (Result: exit-code) since Wed 2016-01-27 16:10:11 JST; > 41min ago > Process: 8356 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 > || /bin/kill -TERM $MAINPID (code=exited, status=1/FAILURE) > Process: 17751 ExecReload=/bin/sh -c /usr/sbin/rndc reload > /dev/null > 2>&1 || /bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) > Process: 9723 ExecStart=/usr/sbin/named -u named $OPTIONS (code=exited, > status=0/SUCCESS) > Process: 9206 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" > == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; else echo > "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE) > Main PID: 9445 (code=exited, status=0/SUCCESS) > CGroup: /system.slice/named.service > > Jan 27 16:10:11 localhost.localdomain bash[9206]: zone > localhost.localdomain/IN: loaded serial 0 > Jan 27 16:10:11 localhost.localdomain bash[9206]: zone localhost/IN: > loaded serial 0 > Jan 27 16:10:11 localhost.localdomain bash[9206]: 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 > Jan 27 16:10:11 localhost.localdomain bash[9206]: zone > 1.0.0.127.in-addr.arpa/IN: loaded serial 0 > Jan 27 16:10:11 localhost.localdomain bash[9206]: zone 0.in-addr.arpa/IN: > loaded serial 0 > Jan 27 16:10:11 localhost.localdomain bash[9206]: zone > individualmoto.ddns.net/IN: loaded serial 2016012700 > Jan 27 16:10:11 localhost.localdomain bash[9206]: zone > 217.194.125.in-addr.arpa/IN: loaded serial 2016012700 > Jan 27 16:10:11 localhost.localdomain systemd[1]: named.service: control > process exited, code=exited status=1 > Jan 27 16:10:11 localhost.localdomain systemd[1]: Failed to start Berkeley > Internet Name Domain (DNS). > Jan 27 16:10:11 localhost.localdomain systemd[1]: Unit named.service > entered failed state. > The "Process: 9206" line shows that named.service tries to verify your configuration using `named-checkconf`, and that this check failed. Use `systemctl status named -n 100` or `journalctl -b -u named` to get more lines from the logs; they will show the actual errors. (Or, run `named-checkzone -z` manually.) The rest isn't a systemd problem. -- Mantas Mikulėnas <[email protected]>
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
