UI Design: include inputs for name server, host IP, DNSSEC

[brooksr4]

This ticket is an outcome of #817.

Story

As a Domain manager OR CISA Analyst/SuperUser I want to update all my DNS-related Data with the correct information so that my website/infrastructure is correctly linked to my .gov domain

Requirements

• [x] Implemented on or about /domain/{nn}/nameservers page
• [x] Facilitate the entry of alpha-numeric DNS name servers. (ex., ns1.example.com) {UI already done}
• [x] Facilitate the entry of IP addresses associated with name server, when NS is a subdomain of the requested domain.
• [x] Facilitate the entry of DNSSEC data records for the group of DNS entries, per the following:

  There are two types of DNSSEC records, DS Data and DNS Key Data.

• [ ] DS Data fields: The DSDATA record contains a cryptographic hash of a DNSKEY record.

  KeyTag - A short numeric value to identify the record. Algorithm - A DropDown Selector with a list of (selectable) algorithms, from a configurable file. (examples are Diffie-Hellman, RSA/SHA256, etc)

Digest Type - A DropDown Selector with a list of cryptographic hash algorithms, from a configurable file. (examples are SHA-1 or SHA-256

Digest - A text field to hold a cryptographic hash value of the referenced DNSKEY-record.

• [x] DNSKey Data fields: The DNSKEY record contains the public signing key.

  Algorithm - A Dropdown selector with a list of public key's cryptographic algorithm, from a configurable file. (example, RSA/SHA-256) Public Key - An alphanumeric text box for the Public Key Data NOTE: Two other fields exist but are used for backward compatibility. These have fixed values. Flags - Fixed Value of "KSK," (key-signing key) as we are only supporting second level domains. (DO WE NEED TO SUPPORT ZSK as we eventually support subdomains?) Protocol - Fixed value of 3, always. DNSSEC

• Constraints

DNS HOSTS:

• [ ] Enforce a minimum of 2 and maximum of 13 DNS entries.
• [x] A DNS entry which is a subdomain of the target domain must have an associated IP Address
• [x] The IP address associated with a DNS entry may be IPv4 or IPv6. (support both and detect/validate which type) DNSSEC ENTRIES: A Domain manager may optionally utilize DNSSEC, which

Validations

• [x] DNS entries must be verified to properly resolve the Domain to an IP address. (future) Documented in #1036 (later)

Acceptance Criteria

• [x] Domain Management page (/domain/{nn}/nameservers) includes fields for primary, secondary and additional host names and IPs

• [x] Fields are available for DS Data and DNS Data: Key Tag, Algorithm, Digest Type, Digest

Additional Context

This is based on the following screenshot from the Verisign system: https://drive.google.com/file/d/1CkXnRQTcUHTD3lnfnk8VmrsMZV_4UzDy/view?usp=sharing

This affects page: /domain/{xxx}/nameservers, linked in big picture here:

Issue Links

🔄 Relates to: #817 Blocks: #1016 Figma designs

Clarifying Requirements in Slack Thread: https://cisa-corp.slack.com/archives/C05BDEA3C11/p1694524933555419

[abroddrick]

@PaulKuykendall this is the DS data we talked about today. This should be moved up in priority and dealt refined async so it can be slotted for sooner rather than later. Can we add this to the top of priority for design?

[abroddrick]

For refinement: can we please separate the dev portion and the content/design portion into separate tickets? This will make it easier to track the progress and allow us to add points to each separately

[abroddrick]

Refinement Q: for ips epp accepts ip4 or ip6 as values when adding the ip to host. Should there be a dropdown with two values ip4/ip6 next to the ip address fields so a user can set which is applicable? Or just default to using ip6?

[h-m-f-t]

It'd be ideal to detect when a given address was (valid) v4 or v6, but in the absence of that having a user-selectable field defining the type would work.

[PaulKuykendall]

Paul - research actual fields required, and think thru entire slice.

[gabydisarli]

@PaulKuykendall Confused on this screencap of a drop down for Digest. On the Verisign screencap I see an open field for Digest, not a drop down.

[PaulKuykendall]

@gabydisarli - My mistake. I mis-labeled that in the above reference. I've corrected it. that dropdown SHOULD have been under DS/DNS Data Algorithm.

[gabydisarli]

added Figma design links. Figma designs are mostly done but small tweaks to copy here and there are happening in tandem with development

[gabydisarli]

Name servers page is complete and linked in associated dev ticket. There is still one small copy change pending but marking this done as it's 99% there.

[gabydisarli]

I will be making a new flow for DNSSEC without Keydata, that work is tracked in this ticket #1147