我试图build立命名,但我很难试图解决它。 我在CentOS 7.2-1511上使用了bind-9.9.4-29.el7_2.3.x86_64,这就是我在systemctl start命名时发生的情况:
[root@berlin ~]# 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. [root@berlin ~]# journalctl -xe -- Subject: Unit named-setup-rndc.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named-setup-rndc.service has finished starting up. -- -- The start-up result is done. sep 01 12:35:56 berlin systemd[1]: Starting Berkeley Internet Name Domain (DNS)... -- Subject: Unit named.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named.service has begun starting up. sep 01 12:35:56 berlin bash[4808]: zone 184.132.10.IN-ADDR.ARPA/IN: loaded serial 2 sep 01 12:35:56 berlin bash[4808]: zone 7.237.10.IN-ADDR.ARPA/IN: loaded serial 2 sep 01 12:35:56 berlin bash[4808]: zone 1.168.192.IN-ADDR.ARPA/IN: loaded serial 3 sep 01 12:35:56 berlin bash[4808]: zone 1.1.10.IN-ADDR.ARPA/IN: loaded serial 6 sep 01 12:35:56 berlin bash[4808]: zone intra.genaker.net/IN: loaded serial 17 sep 01 12:35:56 berlin bash[4808]: zone localhost.localdomain/IN: loaded serial 0 sep 01 12:35:56 berlin bash[4808]: zone localhost/IN: loaded serial 0 sep 01 12:35:56 berlin bash[4808]: 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: NS '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 sep 01 12:35:56 berlin bash[4808]: 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: not loaded due to errors. sep 01 12:35:56 berlin bash[4808]: _default/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: bad zone sep 01 12:35:56 berlin bash[4808]: zone 1.0.0.127.in-addr.arpa/IN: NS '1.0.0.127.in-addr.arpa' has no address records (A or AAAA) sep 01 12:35:56 berlin bash[4808]: zone 1.0.0.127.in-addr.arpa/IN: not loaded due to errors. sep 01 12:35:56 berlin bash[4808]: _default/1.0.0.127.in-addr.arpa/IN: bad zone sep 01 12:35:56 berlin bash[4808]: zone 0.in-addr.arpa/IN: NS '0.in-addr.arpa' has no address records (A or AAAA) sep 01 12:35:56 berlin bash[4808]: zone 0.in-addr.arpa/IN: not loaded due to errors. sep 01 12:35:56 berlin bash[4808]: _default/0.in-addr.arpa/IN: bad zone sep 01 12:35:56 berlin systemd[1]: named.service: control process exited, code=exited status=1 sep 01 12:35:56 berlin systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). -- Subject: Unit named.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named.service has failed. -- -- The result is failed. sep 01 12:35:56 berlin systemd[1]: Unit named.service entered failed state. sep 01 12:35:56 berlin systemd[1]: named.service failed. sep 01 12:35:56 berlin polkitd[4091]: Unregistered Authentication Agent for unix-process:4801:15030793 (system bus name :1.119, object path /org/freedesktop/PolicyKit1/Authenti
然后,如果我做一个named-checkconf,我可以得到:
[root@berlin ~]# named-checkconf -z /etc/named.conf zone 184.132.10.IN-ADDR.ARPA/IN: loaded serial 2 zone 7.237.10.IN-ADDR.ARPA/IN: loaded serial 2 zone 1.168.192.IN-ADDR.ARPA/IN: loaded serial 3 zone 1.1.10.IN-ADDR.ARPA/IN: loaded serial 6 zone intra.genaker.net/IN: loaded serial 17 zone localhost.localdomain/IN: loaded serial 0 zone localhost/IN: loaded serial 0 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: NS '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' has no address records (A or AAAA) 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: not loaded due to errors. _default/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: bad zone zone 1.0.0.127.in-addr.arpa/IN: NS '1.0.0.127.in-addr.arpa' has no address records (A or AAAA) zone 1.0.0.127.in-addr.arpa/IN: not loaded due to errors. _default/1.0.0.127.in-addr.arpa/IN: bad zone zone 0.in-addr.arpa/IN: NS '0.in-addr.arpa' has no address records (A or AAAA) zone 0.in-addr.arpa/IN: not loaded due to errors. _default/0.in-addr.arpa/IN: bad zone
一些帮助将不胜感激。 谢谢。
阿尔伯特
非常感谢你的回答, 尼尔 。 这是我的/etc/named.rfc1912.zones
[root@berlin etc]# cat named.rfc1912.zones // named.rfc1912.zones: // // Provided by Red Hat caching-nameserver package // // ISC BIND named zone configuration for zones recommended by // RFC 1912 section 4.1 : localhost TLDs and address zones // and http://www.ietf.org/internet-drafts/draft-ietf-dnsop-default-local-zones-02.txt // (c)2007 RW Franks // // See /usr/share/doc/bind*/sample/ for example named configuration files. // zone "localhost.localdomain" IN { type master; file "named.localhost"; allow-update { none; }; }; zone "localhost" IN { type master; file "named.localhost"; allow-update { none; }; }; 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 { type master; file "named.loopback"; allow-update { none; }; }; zone "1.0.0.127.in-addr.arpa" IN { type master; file "named.loopback"; allow-update { none; }; }; zone "0.in-addr.arpa" IN { type master; file "named.empty"; allow-update { none; }; };
请告诉我你是否需要/ var / named内的区域文件。 谢谢。
journalctl和named-checkconf都会告诉你为什么你的named不会启动:
_default/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: bad zone _default/1.0.0.127.in-addr.arpa/IN: bad zone _default/0.in-addr.arpa/IN: bad zone
换句话说:三个反向区域文件不能正确写入。
他们甚至告诉你什么BIND不喜欢这些区域文件:
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: NS '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' has no address records (A or AAAA) zone 1.0.0.127.in-addr.arpa/IN: NS '1.0.0.127.in-addr.arpa' has no address records (A or AAAA) zone 0.in-addr.arpa/IN: NS '0.in-addr.arpa' has no address records (A or AAAA)
因此,您似乎指定了这些区域的名称服务器,但没有确定它们是否真实存在,或者是在这些名称服务器logging中input了拼写错误,以便指定其他内容而不是您想要的内容。
检查这三个区域文件,特别注意NSlogging。 如果找不到错误,请发布一条或所有条目,以便社区可以查看。