*编辑1 *在更多的debuggingloggingmonkeying后，我看到一些感兴趣的日志条目。
27-Jul-2012 23:45:26.537 general: error: zone example.lan/IN/internal: journal rollforward failed: no more 27-Jul-2012 23:45:26.537 general: error: zone example.lan/IN/internal: not loaded due to errors. ^^^如果我能补救上面的消息，我想我会很好去^^^
*编辑2 *抓在秸秆我碰了一个正向和反向区日记文件，并重新命名。 繁荣！ 作品。 尽pipe文档说明文件是自动创build的，我之前见过的…不知道为什么，但这个伎俩。 还重新检查了目录中的烫发文件。与我一样，他们是正确的，命名为rw。
基本的DHCP和DNSfunction在192.168.111.2上。 客户端按预期分配地址，并可以parsing本地DNS名称以及Internet名称。 我的问题是，没有创build命名的区日记文件。
我尝试将区域文件放置在不同的目录中（/ var / named / data，/ var / named，/ var / named / dynamic – 无论哪个dir命名为拥有并且开放的perms我现在都无处）。 在这个过程中，我一度得到了一个拒绝，当命名试图创build日记。 解决了这个问题：
那个杂志就这样被创造出来，这里就是事情崩溃的地方。 我试图驯服权限，以更理智的和破坏它。 一旦改变，并重新启动命名它抛出一个错误，指示日记不同步（或影响）…不要紧，因为这是一个新的设置，所以我删除它，现在不重新创build。 现在，尽pipe我在/ var / log / messages，chrooted /var/log/named.log或chrooted /var/log/named.debug中看不到任何错误。 我用“rndc trace”增加了debugging级别 – 没有爱。 追踪到10，仍然没有。
SELinux被禁用…
[root@server temp]# sestatus SELinux status: disabled
dhcpd.conf中…
allow client-updates; ddns-update-style interim; subnet 192.168.111.0 netmask 255.255.255.224 { ... key dhcpudpate { algorithm hmac-md5; secret LDJMdPdEZED+/nN/AGO9ZA==; } zone example.lan. { primary 192.168.111.2; key dhcpudpate; } }
named.conf中…
key dhcpudpate { algorithm hmac-md5; secret "LDJMdPdEZED+/nN/AGO9ZA=="; }; zone "example.lan" { type master; file "/var/named/dynamic/example.lan.db"; allow-transfer { none; }; allow-update { key dhcpudpate; }; notify false; check-names ignore; };
以下显示了/var/log/named.log输出的命名启动 – 没有错误。
27-Jul-2012 21:33:39.349 general: info: zone 111.168.192.in-addr.arpa/IN/internal: loaded serial 2012072601 27-Jul-2012 21:33:39.349 general: info: zone example.lan/IN/internal: loaded serial 2012072501 27-Jul-2012 21:33:39.350 general: info: zone example2.lan/IN/internal: loaded serial 2012072501 27-Jul-2012 21:33:39.350 general: info: zone example3.lan/IN/internal: loaded serial 2012072601 27-Jul-2012 21:33:39.350 general: info: zone example4.lan/IN/internal: loaded serial 2012072501 27-Jul-2012 21:33:39.351 general: info: zone example5.lan/IN/internal: loaded serial 2012072501 27-Jul-2012 21:33:39.351 general: info: managed-keys-zone ./IN/internal: loaded serial 0 27-Jul-2012 21:33:39.351 general: info: zone example.lan/IN/external: loaded serial 2012072501 27-Jul-2012 21:33:39.352 general: info: zone example1.lan/IN/external: loaded serial 2012072501 27-Jul-2012 21:33:39.352 general: info: zone example2.lan/IN/external: loaded serial 2012072501 27-Jul-2012 21:33:39.352 general: info: zone example3.lan/IN/external: loaded serial 2012072501 27-Jul-2012 21:33:39.353 general: info: managed-keys-zone ./IN/external: loaded serial 0 27-Jul-2012 21:33:39.353 general: notice: running 27-Jul-2012 21:34:03.825 general: info: received control channel command 'trace 10' 27-Jul-2012 21:34:03.825 general: info: debug level is now 10
…和/ var / log / messages命名的开始…
Jul 27 23:02:04 server named[9124]: ---------------------------------------------------- Jul 27 23:02:04 server named[9124]: BIND 9 is maintained by Internet Systems Consortium, Jul 27 23:02:04 server named[9124]: Inc. (ISC), a non-profit 501(c)(3) public-benefit Jul 27 23:02:04 server named[9124]: corporation. Support and training for BIND 9 are Jul 27 23:02:04 server named[9124]: available at https://www.isc.org/support Jul 27 23:02:04 server named[9124]: ---------------------------------------------------- Jul 27 23:02:04 server named[9124]: adjusted limit on open files from 4096 to 1048576 Jul 27 23:02:04 server named[9124]: found 2 CPUs, using 2 worker threads Jul 27 23:02:04 server named[9124]: using up to 4096 sockets Jul 27 23:02:04 server named[9124]: loading configuration from '/etc/named.conf' Jul 27 23:02:04 server named[9124]: using default UDP/IPv4 port range: [1024, 65535] Jul 27 23:02:04 server named[9124]: using default UDP/IPv6 port range: [1024, 65535] Jul 27 23:02:04 server named[9124]: listening on IPv4 interface eth0, 192.168.111.2#53 Jul 27 23:02:04 server named[9124]: generating session key for dynamic DNS Jul 27 23:02:04 server named[9124]: sizing zone task pool based on 12 zones Jul 27 23:02:04 server named[9124]: set up managed keys zone for view internal, file 'dynamic/3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys' Jul 27 23:02:04 server named[9124]: set up managed keys zone for view external, file 'dynamic/3c4623849a49a53911c4a3e48d8cead8a1858960bccdea7a1b978d73ec2f06d7.mkeys' Jul 27 23:02:04 server named[9124]: command channel listening on 127.0.0.1#953
我能做些什么来进一步解决这个问题？ 几乎看起来好像dhcpd没有触发更新。 也许我应该在这里排除故障，如果是的话，怎么样？
非常感谢。
我有同样的问题
Nov 24 15:05:04 zserver named[1020]: error (network unreachable) resolving './NS/IN': 2001:dc3::35#53 Nov 24 15:05:04 zserver named[1020]: error (network unreachable) resolving 'whois.verisign-grs.com/A/IN': 2001:7fd::1#53 Nov 24 15:05:04 zserver named[1020]: error (network unreachable) resolving 'whois.verisign-grs.com/AAAA/IN': 2001:503:ba3e::2:30#53 Nov 24 15:05:04 zserver named[1020]: error (network unreachable) resolving 'whois.verisign-grs.com/A/IN': 2001:dc3::35#53 Nov 24 15:05:04 zserver named[1020]: error (network unreachable) resolving 'whois.verisign-grs.com/AAAA/IN': 2001:7fd::1#53 Nov 24 15:05:04 zserver named[1020]: error (network unreachable) resolving 'whois.verisign-grs.com/AAAA/IN': 2001:dc3::35#53
这个问题对我来说是我的eth0是默认网关（BEFORE）
Destination Gateway Genmask Flags Metric Ref Use Iface 172.16.123.0 * 255.255.255.0 U 0 0 0 eth1 link-local * 255.255.0.0 U 1002 0 0 eth0 link-local * 255.255.0.0 U 1003 0 0 eth1 10.0.0.0 * 255.0.0.0 U 0 0 0 eth0 default zserver.Stanton 0.0.0.0 UG 0 0 0 eth0
我手动添加一个路由与外部网关（AFTER）
route add default gw ip address Destination Gateway Genmask Flags Metric Ref Use Iface 172.16.123.0 * 255.255.255.0 U 0 0 0 eth1 link-local * 255.255.0.0 U 1002 0 0 eth0 link-local * 255.255.0.0 U 1003 0 0 eth1 10.0.0.0 * 255.0.0.0 U 0 0 0 eth0 default 172.16.123.1 0.0.0.0 UG 0 0 0 eth1 default zserver.Stanton 0.0.0.0 UG 0 0 0 eth0
从Windows客户端做了nslookup
Nov 24 15:27:58 zserver named[1020]: client 10.10.100.1#57727: RFC 1918 response from Internet for 1.123.16.172.in-addr.arpa