NTP没有正确地在池服务器上处理限制

If I am running ntp (via ntp.conf) heavily restricted, I cannot use a pool for a server. Why? Because the call to restrict (to allow access for the pool) seems to be another DNS Lookup, which returns another IP value than what was used to originally call the server. Please show me that I am wrong/being stupid about this.

如果我正在运行严重受限制的ntp(通过ntp.conf)，则不能为服务器使用池。为什么?因为限制(允许对池进行访问)的调用似乎是另一个DNS查找，它返回的IP值比最初调用服务器的IP值要多。请让我知道我错了。

Crude Example (portion of ntp.conf):

粗略示例(ntk .conf的一部分):

server 0.debian.pool.ntp.org iburst
restrict default ignore
restrict -6 default ignore
restrict 0.debian.pool.ntp.org mask 255.255.255.255 nomodify notrap noquery

This does not work (I think) because DNS calls to 0.debian.pool.ntp.org return different IP addresses and thus the wrong IP address is allowed via the (poorly named) restrict.

这是行不通的(我认为)，因为DNS调用0.debian.pool.ntp.org会返回不同的IP地址，因此通过(命名不佳)限制允许错误的IP地址。

1 个解决方案

#1

Use the builtin source alias/directive/whatever:

使用内置源别名/指令/无论什么:

restrict source nomodify notrap noquery

Updatedd to include documentation for source:

更新为包含源文件:

restrict source configures a template restriction automatically added
at runtime for each association, whether configured, ephemeral, or
preemptible, and removed when the association is demobilized.

From: http://www.eecis.udel.edu/~mills/ntp/html/accopt.html#restrict

来自:http://www.eecis.udel.edu/ ~米尔斯/国家结核控制规划/ html / accopt.html #限制

1 个解决方案

#1

更多相关文章

随机推荐