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

What's the expected behavior with BIND slave that's been offline for some time?

· 52CE 我爱测

We have a situation where a BIND slave server was not able to write any zone data to the file system. When this server was rebooted and BIND restarted it started with an older version of the zone files than what was currently on …

问题原文

原帖链接 · slm · CC BY-SA 4.0

We have a situation where a BIND slave server was not able to write any zone data to the file system. When this server was rebooted and BIND restarted it started with an older version of the zone files than what was currently on the master.

During this time it was able to receive IXFR transfers from the master, it just couldn't persist these changes to the HDD.

This got me wondering about what is the expected behavior with a BIND server? It seems like a bit of a design flaw that it wouldn't do some checking with its master, prior to entering service.

For reference this is the version of bind on the slave side:

$ rpm -q bind
bind-9.8.2-0.47.rc1.el6_8.2.x86_64

I did find this reference:

Which states the following:

Zone notifies and refreshes

Apart from when a server is restarted, or when rndc commands are used to force a zone transfer, there are two mechanisms that cause slave servers to check whether or not their copy of a zone is current. The process of checking and updating is called a zone refresh :

I interpret this as BIND not doing anything special when in its start up phase.

已采纳解答

原帖链接 · slm · CC BY-SA 4.0

Hmm, didn't read all the docs completely. There's a paragraph that states the following on the same page:

When a server is restarted, it sends out notifications for the zones that it has loaded (in case they have been updated while it was not running). Similarly, when loading zones that are slaved, a newly-restarted named will initiate a refresh for each zone (using jittered time intervals so that all refreshes are not initiated concurrently).

So from this it sounds like the BIND slaves will send out a notification to the master and then coordinate IXFRs to catch up and begin serving updated zone information.

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

资料来源与适用范围

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

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

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