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!
Accepted Answer
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!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.