Hi, I’m not sure if the WHOIS registrar status is applicable to this case.
If you made recent changes to how your DNS is configured, you might consider reverting them.
But if you want to move forward and fix things so you can use DO’s DNS service, I looked into it a little further.
The domain looks OK and I see that it is delegated to the DigitalOcean nameservers:
Name Server: NS1.DIGITALOCEAN.COM
Name Server: NS2.DIGITALOCEAN.COM
Name Server: NS3.DIGITALOCEAN.COM
However, if I do a dig against the DO nameserver for “NS” (nameserver) records they are not set to DO nameservers:
dig @ns1.digitalocean.com beachvolley.academy NS
; <<>> DiG 9.10.6 <<>> @ns1.digitalocean.com beachvolley.academy NS
;; ANSWER SECTION:
beachvolley.academy. 1800 IN NS ns1.beget.pro.
beachvolley.academy. 1800 IN NS ns2.beget.pro.
beachvolley.academy. 1800 IN NS ns2.beget.com.
beachvolley.academy. 1800 IN NS ns1.beget.com.
One way to correct this would be to follow this tutorial:
How To Point to DigitalOcean Nameservers From Common Domain Registrars
If you do this, you will need to create all the records you need - eg, a CNAME or A record for your website. If you use mail on that domain, you’d need to create MX records, etc.
I hope this helps, please let us know if you have more questions or run into problems - good luck!
DNS is the naming system that is used to bind a domain name to a web server. In this guide, we will change the nameservers for a domain that we have registered and point it to a DigitalOcean Droplet.