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

Syncronize SOA serial numbers explanation

· 52CE 我爱测

I made two successive mistakes while updating zone records. Once I forgot to increment the serial number, then next time I did put a digit more ie 20170210111 instead of 2017021011 , and each time I reloaded config : rndc reload …

问题原文

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

I made two successive mistakes while updating zone records. Once I forgot to increment the serial number, then next time I did put a digit more ie 20170210111 instead of 2017021011, and each time I reloaded config : rndc reload.

When I realised it, I switched back serial to a 10 digits number, so my zone file SOA serial is now 2017021012.

I get this now :

#  host -C domain.tld
Nameserver X.X.X.X:
        domain.tld has SOA record X.X.X.X.ovh.net. postmaster.domain.tld. 2017021010 28800 7200 1209600 3600
Nameserver Y.Y.Y.Y: 
        domain.tld has SOA record X.X.X.X.ovh.net. postmaster.domain.tld. 2017021003 28800 7200 1209600 86400

Where X.X.X.X is my primary DNS server IP and Y.Y.Y.Y secondary one.

I'm not really used to DNS configuration, and I really don't know how to resynchronize serials and permit propagation. I read already a lot of posts, I'm afraid I still don't know if I should give zone record a greater number, what happened when I reloaded with 13 digits...?

已采纳解答

原帖链接 · Håkan Lindqvist · CC BY-SA 3.0

Since 20170210111 is outside the range of a 32 bit integer, presumably the zone failed to load with the impossible to represent SOA record (check your logs).

First of all, verify (using eg dig @master example.com SOA +norec) that the master is now responding properly and with the current serial (2017021012). If not, rndc reload triggers a reload.

When the master works properly, the slaves should update on their next refresh (based on the SOA REFRESH interval). Also, assuming that the slaves are notify-aware and with proper configuration, you should be able to trigger an immediate refresh using rndc notify example.com, as well as automatically when loading a new version of the zone.

If this doesn't work I would think that your problem is something beyond having had an unloadable zone for a while.

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

资料来源与适用范围

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

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

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