Digital Ocean's ns3 is misconfigured?
ns3.digitalocean.com
ns3.digitalocean.com
dig +noall +answer @ns3.digitalocean.com -t ns digitalocean.com
digitalocean.com. 1800 IN NS ns2.digitalocean.com.
digitalocean.com. 1800 IN NS ns3.digitalocean.com.
digitalocean.com. 1800 IN NS ns1.digitalocean.com.
dig +noall +answer -t soa digitalocean.com
digitalocean.com. 3600 IN SOA kim.ns.cloudflare.com. dns.cloudflare.com. 2263777094 10000 2400 604800 3600
They could probably point the https listener to a landing/parking page unless this supposed to be a DoH endpoint but I doubt that is the intention. Have you opened a ticket with them to inquire?Figured this might be related but guess not (I'm admittedly kinda ignorant around the intricacies of DNS, hence the question mark in the title).
Well that's not good. Lets hope they have an audit trail that can tell you what went wrong. Without the details of your domain I could only guess. I'm sure they and cloudflare together could help you figure it out.