After the DNS incident at DigitalOcen, my domain is no more loading at browser

I’m working on LAMP stack. Developing a application using Laravel. The server has virtual-host set up. None of the domain is opening at browser or taking too long time. The browser error is, “time out”. After the incident of DNS issue at Sep-06-2019, this is behaving like this. I restored the image 7 days back and it’s worked. Again after happen another DNS incident, it’s not working.
How yo fix and troubleshoot this issue.

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.


If lynx is already installed, then most probably you need to adjust the path from where it’s executed. To solve the problem, adjust the path to lynx in the apachectl file, to wherever the lynx binary is installed, or you can add it to your PATH environment variable. If lynx has been installed and apachectl is configured to call lynx properly, there will not be a status report if apache is not running.

Thanks for the checking. I have only set up A record and no other Record. Check the attachment and could you suggest how to tackle it.

Hi @shahinkazi1,

There are a few options at this. Let’s start with them so that you can start troubleshooting

First option

Are you sure, your DNS is properly configured? You are using only one Nameservers, without root CNAME records and only one root A record, correct?

If that’s correct, then the issue is most probably not with the DNS