我正在尝试将 Knot DNS 设置为在 Windows 2019 上运行的主服务器的从属 DNS 服务器（在此示例中为 ip 192.168.77.1）。我想在此从服务器上保留几个内部区域的“副本”，以防主服务器不可用。设置如下：
KnotDNS 2.4.0。@ Debian 9
配置如下：
server:
listen: 0.0.0.0@53
acl:
- id: notify_from_master
address: 192.168.77.1
action: notify
remote:
- id: master
address: 10.234.77.1@53
zone:
- domain: int.example.com
storage: /var/lib/knot/
master: master
acl: notify_from_master
log:
- target: stdout
any: info
挑战在于我无法刷新区域
- 收到船长通知后
2019-09-02T12:17:46 info: [int.example.com.] notify, incoming, 192.168.77.1@55212: received, serial 395
2019-09-02T12:17:46 info: [int.example.com.] refresh, outgoing, 191.168.77.1@53: remote serial 395, zone is outdated
2019-09-02T12:17:46 warning: [int.example.com.] refresh, remote 'master' not usable
2019-09-02T12:17:46 error: [int.example.com.] refresh, failed (no usable master)
- 或致电
knotc zone-refresh int.example.com
2019-09-02T12:39:57 info: [int.example.com.] control, received command 'zone-refresh'
2019-09-02T12:39:57 info: [int.example.com.] refresh, outgoing, 10.234.77.1@53: remote serial 397, zone is outdated
2019-09-02T12:40:07 warning: [int.example.com.] refresh, remote 'master' not usable
2019-09-02T12:40:07 error: [int.example.com.] refresh, failed (no usable master)
但我可以在任何时候选择重新成功转移该区域！knotc zone-retransfer int.example.com
2019-09-02T12:41:32 info: [int.example.com.] control, received command 'zone-retransfer'
2019-09-02T12:41:32 info: [int.example.com.] AXFR, incoming, 192.168.77.1@53: starting
2019-09-02T12:41:32 info: [int.example.com.] AXFR, incoming, 192.168.77.1@53: finished, 0.00 seconds, 1 messages, 6382 bytes
2019-09-02T12:41:32 info: [int.example.com.] refresh, outgoing, 192.168.77.1@53: zone updated, serial 396 -> 397
2019-09-02T12:41:32 info: [int.example.com.] zone file updated, serial 396 -> 397
我不是专家——实际上，我可能恰恰相反。刷新与重新传输有很大不同吗？是否可以将 Windows 2019 服务器作为主服务器，将 Knot 作为从服务器？除了经常使用 cron 调用之外，我还有更好的选择吗knotc zone-retransfer xxx？这可能有效——但它看起来最多也只是笨拙的 :(