First off, check and double-check that the DS
record(s) you are working with correspond the correct keys that are used to sign the zone (or sign the keys that sign the zone). Adding the DS
record signals to everyone that the zone is signed with the corresponding key, and if that DS
data is incorrect, the zone stops working at that point.
The order of the fields in the DS
record data is:
<keytag> <algorithm> <digesttype> <digest>
In the question you show having multiple DS
records, but practically at this time what you really want to add is most likely just the digest type 2 (SHA256) DS
record.
The guidance for choosing DNSSEC algorithms in RFC8624 (from 2019, still of value at this time) covers both recommended DNSKEY
algorithms as well as DS
algorithms.
(Short version: DS
: almost certainly 2/SHA256, DNSKEY
: probably 13/ECDSAP256SHA256, or maybe 15/ED25519, or maybe 8/RSASHA256)
As for the registrar-provided interface for adding a DS
record, the details will vary by registrar. Using the fields as mentioned in the question, I took the current com
DS
just to have an example with real values to work with:
com. 86400 IN DS 30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
That would translate to your fields in the question as:
- Digest: E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
- Key Tag: 30909
- Digest Type: 2
(2 translates to SHA-256, see the relevant registry for this parameter)
- Algorithm: 8
(8 translates to RSA/SHA-256, see the relevant registry for this parameter)