Issues with DNS Server

[seanb1]

My domain is: www.swamember.com

I was using Digital Ocean as my server, it was supposed to install Wordpress one click installation but something went wrong

It produced this output: Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: swamember.com
Type: dns
Detail: DNS problem: SERVFAIL looking up A for swamember.com - the domain's nameservers may be malfunctioning; DNS problem: SERVFAIL looking up AAAA for swamember.com - the domain's nameservers may be malfunctioning

Domain: www.swamember.com
Type: dns
Detail: DNS problem: SERVFAIL looking up CAA for swamember.com - the domain's nameservers may be malfunctioning

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet

My hosting provider, if applicable, is: Digital Ocean

I can login to a root shell on my machine (yes or no, or I don't know): I don't know

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

[danb35]

@seanb1

Domain: swamember.com

Do you own this domain? Because there don't seem to be any DNS records published for it. You'll need to have valid DNS records in place before you'll be able to get a cert.

[seanb1]

yeap! I bought this domain from godaddy

[seanb1]

just wondering if it could be propagation time issue? As I just swapped my DNS host server to digital cloud today

[Nummer378]

You have changed the nameserver to DigitalOcean, but DigitalOcean doesn't think it's responsible for the domain:

dig A swamember.com @ns1.digitalocean.com
; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> A swamember.com @ns1.digitalocean.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 30805
...

You need to look into the domain's setup on DO and fix things there.

[seanb1]

Thanks!! Am looking through the DO control and guides now... but it doesn't seem like I can do much beside adding a domain to connect to my site..