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

Why does bind allow TTL to be set record by records if different TTLs are not allowed within the same record set

· 52CE 我爱测

Why does bind allow TTL to be set record by records if different TTLs are not allowed within the same record set? If i set the zone ttl using: $TTL 39600 And then set a record TTL using: @ 300 IN A 1.1.1.1 I get the warning in my…

问题原文

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

Why does bind allow TTL to be set record by records if different TTLs are not allowed within the same record set?

If i set the zone ttl using:

$TTL 39600

And then set a record TTL using:

@        300     IN      A       1.1.1.1

I get the warning in my logs:

TTL set to prior TTL (300)

This is because I have "Different TTLs for records within the same record set, this is not allowed"

If this is not allowed, whats the point of being able to set TTL record by record?

Thanks

已采纳解答

原帖链接 · Falcon Momot · CC BY-SA 3.0

The file format is specified in RFC1034 and parts of RFC1035. It is very old (1987), and not specifically defined for BIND or in light of current features. There is no great wisdom to be had here; it's like that by convention.

The format is also designed to be used for things like caches, I believe, though in practice this usage must be terribly rare. In a record cache, TTLs differ often and the cache contains records from many different domains.

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

资料来源与适用范围

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

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

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