My domain is: http://www.yor.gr/
I ran this command:
sudo certbot --nginx -d yor.gr -d www.yor.gr
It produced this output:
Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Detail: DNS problem: SERVFAIL looking up A for yor.gr - the domain's nameservers may be malfunctioning; DNS problem: SERVFAIL looking up AAAA for yor.gr - the domain's nameservers may be malfunctioning
My web server is (include version):
nginx version: nginx/1.24.0 (Ubuntu)
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
istributor ID: Ubuntu
Description: Ubuntu 23.10
I can login to a root shell on my machine (yes or no, or 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):
Certbot cannot find A record for yor.gr - the error message informs me. I use Digital Ocean as a hoster.
There is something that caught my attention. In the digital Ocean control panel I can create an A record for www.yor.gr but not for yor.gr - input validation does not allow me to do so. I cannot understand why.
And I do not know if what I am describing above is the cause of the issue.
So you could say this is a DO problem, I am posting here first just to make sure is not sth else.
Whatever nameservers are authoritative for your domain need to respond with an A record, pointing to the appropriate IP address. Right now, it doesn't look like you have any authoritative nameservers for your domain--you need to fix that, likely with whoever you bought the domain from:
That's important, and you need to figure out how to fix it, but it's less important than the fact that you don't have NS records. NS records tell the Internet what nameservers it should use to resolve your domain, and there are no such records. Without them, you can do whatever you want on DO, and it won't have any effect.
Yeah, your DNS zone is misconfigured. I have no clue how that works with DigitalOcean, but for some reason you only have access to the DNS zone for www.yor.gr and DigitalOcean thinks the DNS zone for yor.gr does not exist. At least not on their DNS servers.
You want a DNS zone for yor.gr where you can add things for yor.gr and also the subdomain www.
Sorry...I cannot follow you....if you could elaborate a little.
DNS is separated in "zones". For simple setups you've got the root zone ., the TLD zone (gr.) and the zone for the domain name (yor.gr). Each have their own SOA RR. Within a zone you can have multiple subdomains. For TLDs this would be new/other zones with their own SOA RR, but for a simple domain such as yor.gr, that zone would just have some subdomains like www with a A or perhaps a CAA RR for the zone origin itself (e.g. yor.gr).
For some reason, DigitalOcean does not think the yor.gr domain is a DNS zone on their DNS servers. It seems you can only change things within the DNS zone www.yor.gr which usually is not even a complete DNS zone, but just a single A RR or sometimes perhaps an extra AAAA RR. Not a complete DNS zone with SOA RR and NS RRs.
How am I suppose to do that?...I have no idea at all.
I don't know either. I don't have any experience with DigitalOcean, I have no clue how their configuration system looks like, which options you have. Or not have. You might need to contact Digital Ocean about this.
If it's a "second domain", you really didn't solve it; things are still badly misconfigured. yor.gr should be the only domain; www.yor.gr is a subdomain. It shouldn't have its own NS records (it does).