大网数据广告活动
服务器运维问答

DDNS, BIND and leftover .jnl files

· 52CE 我爱测

I have configured BIND and ISC DHCPD to work together (using keys for updates). Now it's not that it does not work at all: forward maps etc are most often added. However, very often, for no apparent reason the .jnl file (journal)…

问题原文

原帖链接 · LetMeSOThat4U · CC BY-SA 3.0

I have configured BIND and ISC DHCPD to work together (using keys for updates). Now it's not that it does not work at all: forward maps etc are most often added.

However, very often, for no apparent reason the .jnl file (journal) for the zone is left there and the main zone file is not updated. This results in infuriating lack of resolution of some hosts after DHCP lease acquire (if the hosts was not there in the zone file in the first place, or it leads to the old address).

Permissions look like this:

-rw-r--r--   1 bind bind  691 Dec 10 11:06 myzone.zone
-rw-r--r--   1 bind bind  765 Dec 10 12:17 myzone.zone.jnl

It should not be permissions problem though since the zone does (often) get updated via DHCP/DDNS?

What is the source of this problem and a fix for it?

OS: debian 7.2 x64, stable release bind and isc-dhcp server.

社区高分解答

原帖链接 · Craig Leres · CC BY-SA 3.0

With bind 9.9, "rndc sync" is not enough; you also need the "-clean" flag:

sync [-clean] [zone [class [view]]]
Sync changes in the journal file for a dynamic zone to the master file. If the "-clean" option is specified, the journal file is also removed. If no zone is specified, then all zones are synced.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2013-12-10)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。