Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Whois on IRC returns IP instead of domain Question Question
A record pointing external IP is not working Question Question

Question

IP propagations

Posted June 19, 2020 571 views
DNS

Since June 13, godaddy correctly updated the domain nameservers to:

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

5 days have passed and the IP has not yet propagated correctly, I am having problems because the page is not displaying in some places. Do I have something wrong in the domain configuration in digitalocean?

The A record TTL is set 3600

Please i need help. This is my domain: servigestiones.com

Add a comment
juanmdt
By:
juanmdt

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Whois on IRC returns IP instead of domain Question Question
A record pointing external IP is not working Question Question

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.

×
Submit an Answer
2 answers
juanmdt June 20, 2020

i solve my problem. This is what Support told me to do and it works.

.........................................

We’ve reviewed the status of your domain servigestiones.com, and upon review by our Networking team, we found that it has DS (DNSSEC) records configured at the domain registrar. DNSSEC is not currently supported by DigitalOcean DNS, and the implementation of these DS records may be causing disruption with the propagation of your domain through our DNS.

Please try removing the DS records at your domain registrar, and allow some time for the DNS to propagate. If after a few hours you don’t see any improvement, then please try making an arbitrary edit to your DNS zone(add an unnecessary record, for ex test.servigestiones.com) just to give the zone a little push.

Reply Report
alexdo June 19, 2020

Hello, @juanmdt

DNS changes might take up to 72 hours or even more due to ISP cache and normal DNS propagation. Unfortunately, many of those factors are our of your control. When it comes to DNS propagation there is not much you can do except of setting a lower TTL for the DNS records (A records) in order to speed up the process a bit. As mentioned usually the DNS changes take longer time due to DNS cache from all the IPSs.

Tools https://www.whatsmydns.net can help you check if the records have been updated in various locations.

Regards,
Alex

Reply Report

Related

Looking for something else?

Ask a new question Search for more help