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

Managing multiple equal zones with DNSSEC

· 52CE 我爱测

I run an authoritative name server (BIND), and I have a few dozens domain with identical zone files, i.e. they all use /etc/bind/db.default3 . I’m considering deploying DNSSEC on my server, but so far all documentation I found on…

问题原文

原帖链接 · Joachim Breitner · CC BY-SA 3.0

I run an authoritative name server (BIND), and I have a few dozens domain with identical zone files, i.e. they all use /etc/bind/db.default3.

I’m considering deploying DNSSEC on my server, but so far all documentation I found on it would require me to do many manual steps per zone (such as generating KSK and ZSK). BIND 9.9’s inline-signing makes some of it easier, but not everything.

So, can I make BIND, in inline-signing mode, use the same KSK for multiple domains? If so, will I be able to put the same value in the DS record for these domains? And why do I have to manage the ZSK – shouldn’t BIND, given a KSK, be able to take care of that for me?

已采纳解答

原帖链接 · Patrick Mevzek · CC BY-SA 4.0

You can use the same KSK for multiple domains, but it is not a good idea since it means that if there is a problem with this key (either cryptographically, you loose the private key, or you forget to renew it, etc.) it will impact more than one domain. For a given key, you can not have the same DS in multiple zones, since the DS value is computed from both the key and the domain name!

Also, recent attacks against SHA1 (see https://www.dns.cam.ac.uk/news/2020-01-09-sha-mbles.html or https://blog.apnic.net/2020/01/17/sha-1-chosen-prefix-collisions-and-dnssec/ for a full explanation of consequences for DNSSEC) can be mitigated a little if you make sure NOT TO use the same key for multiple zones. ("For extra protection against chosen prefix collision attacks, zones should not share keys, and they should have separate ZSKs and KSKs.")

And as Håkan said in comments, nowadays for new deployments you should use either ECDSAP256SHA256 or RSASHA256 (hence no SHA-1 whatsoever). See RFC 8624 section §3.1 (all SHA-1 versions there are either "MUST NOT" implement or "NOT RECOMMENDED").

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

资料来源与适用范围

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

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

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