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
Droplet upgrading 14.04 -> 15.10 -> 16.04 -> 16.10 -> 17.04 etc? Question Question
Cant ssh into server Question Question

Question

Can't connect to domain from browser but can via web proxy

Posted December 16, 2018 1.1k views
Server OptimizationUbuntu 16.04

Hi Guys,

This is a strange one, i bought a domain from DynaDot: http://www.thebestofxreviews.com/

I cannot access it via my browser i get “Can’t connect to the server” error’s in FifreFox and other browsers, but if i use a web proxy i can see the domain fine, i have done everything correctly to add it to the droplet.

Has anyone come accross this before?

regards

Add a comment
graham23s
By:
graham23s

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
Droplet upgrading 14.04 -> 15.10 -> 16.04 -> 16.10 -> 17.04 etc? Question Question
Cant ssh into server 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
jarland December 17, 2018

Hey friend,

Are you seeing any improvement on this today? My opinion is that it was DNS and would have cleared up by now. My assumption is that you requested the domain before it had fully propagated to the parent TLD, your ISP’s DNS servers cached the lookup, and then waited a normal amount of time before dropping their cache to look for a new record. Meanwhile, using another ISP that had not recently performed a lookup, it had no relevant cache and immediately found the new DNS records at the TLD.

Good rule of thumb for a DNS change is that it takes up to 48 hours for a change to be reflected for everyone attempting to view it (due to DNS caching and TTL values). A new domain can be the same thing.

Jarland

Reply Report
graham23s December 17, 2018

Hello Jarland,

Everything is working well :) i have never come accross that before in all my years working with domains.

Thank you :)

Reply Report

Related

Looking for something else?

Ask a new question Search for more help