Question

Problem creating A record without WWW

Posted on December 7, 2023
Let's Encrypt Networking
Asked by ambicoder

I am trying to get a certificate w let’s encrypt , in doing so I get as a response that no A record is found xxx.gr. So, I tried to create an A record but the validation of the hostname input box does not allow it. Whatever a type just precedes my sitename.

If the input box supposes to work this way then what might be the cause of getting back error message from cerbot?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

KFSys

Site Moderator

• December 7, 2023

Heya @ambicoder,

Yes, you need to point your Domain to your Droplet, where you are running certbot from.

Regarding the addition of the A record, where are you trying to add it, is it DigitalOcean’s Control Panel? If not, I suggest to switch your Nameservers over to DigitalOcean’s:

As soon as you do that, you can follow this tutorial:

https://docs.digitalocean.com/products/networking/dns/how-to/

It will help you setup your DNS. Once you have that you should be able to use certbot to issue the let’s encrypt certificate.

alexdo

Site Moderator

• December 7, 2023

Hello @ambicoder

Are you managing your DNS records from your DigitalOcean account? If that is so you can make sure your domain name is using the following nameservers:

ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

You can also check our docs here on how to set an A record:

https://docs.digitalocean.com/products/networking/dns/how-to/manage-records/#a-records

It will take some time for the name server changes to propagate after you’ve saved them and it goes the same when updating DNS records. During this time, the domain registrar communicates the changes you’ve made with your ISP (Internet Service Provider). In turn, your ISP caches the new name servers to ensure quick site connections. This process usually takes about 30 minutes but could take up to a few hours depending on your registrar and your ISP’s communication methods.

Regards