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

Posted September 11, 2019 1.5k views
LAMP StackDigitalOceanDNSUbuntu 18.04

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.

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
3 answers

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

  • Second option

    Apache is experiencing difficulties. When you try to load the website, do you see anything strange on the server like CPU/Memory Spikes, Apache workers being filled up? I would assume the case is exactly this.

    If you are not sure how to troubleshoot, you can check the following article and this

    All of these help track the traffic, cpu usage and memory usage of your droplet.

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.


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.