Current Behavior

Deleting a domain from the registry through the admin portal will fail if a domain has dnssec enabled with the error message Error deleting this Domain: This subdomain is being used as a hostname on another domain:. This originally appeared to be caused by the existence of DS records that point to the domain, preventing the domain from being deleted. However, some domains still got blocked from deletion even though they never had DNSSEC. To add to this bug, a few domains that never had dnssec were successfully deleted and we are unsure why it works for some and not others

Expected Behavior

Deleting a domain should work with or without it having dnssec or any other data. Deleting a domain from the registry through the admin portal deletes DS Data first, allowing for domains with DNSSec enabled to be successfully deleted. If deleting a DS record fails, then the error message displayed should accurately reflect that it is DS data, not a host, that is preventing the domain from being deleted. All other items connected to this domain should be deleted as well.

Note: there may also be something wrong with the way contacts are deleted.

Steps to Reproduce

1. In a test environment, enable DNSSec on a domain
2. Attempt to delete that domain from the registry in the admin portal

Additional Context

Relevant slack thread

Issue Links

No response