In the past I have created a droplet with a LAMP stack and successfully configured the let’s encrypt certificate using the domain name ‘stage.osn.hepabolu.nl’. Today I deleted the droplet and started over. There is an A record for this same domain name (stage.osn.hepabolu.nl) and it points to the correct droplet IP address. I’ve checked with dig stage.osn.hepabolu.nl @ns1.digitalocean.com and this shows the correct IP address. Yet, the domain name is not visible through other DNSses.
I tried a dummy domain name fliep.hepabolu.nl pointing to the same IP address and created both A and AAAA records, but now we are more than 8 hours later and non of these domain names are propagated. What is going on?
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.
Featured on Community
Get our biweekly newsletter
Sign up for Infrastructure as a Newsletter.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Become a contributor
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hello there,
Looking at the main domain - hepabolu.nl it is using external nameservers meaning the active DNS zone for this domain name is not controlled by your DigitalOcean account but by a third-party provider.
You can either change the nameservers to DigitalOcean’s ones or create/add the A record from the other provider.
Hope that this helps!