Website DNS not resolving. Was resolving over the weekend. Now getting unknown host. No longer pingable

Posted October 1, 2018 2.3k views
UbuntuApacheLAMP StackDNS

My domain (, which I bought last week via Namecheap, is no longer resolving. I had everything setup properly, which was:

  • Setup DNS settings to DO servers in Namecheap
  • Added all correct entries via DO Network settings

As mentioned, everything was working as expected the entire weekend, I was able to login to my wordpress page and work on my site. Today, I tried access the website, no dice. I never made any changes. I checked all configuration just in case, everything is the same. I’m using virtual host on LAMP (Ubuntu), and the other sites are accessible, but not my new site.

Here is the config for the virtual host file:

<VirtualHost *:80>
        ServerAdmin <redacted>
        DocumentRoot /var/www/

        <Directory /var/www/html/>
            Options FollowSymLinks
            AllowOverride All
            Require all granted

        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined

I’m really puzzled as I made zero changes over the weekend and now cannot access the site. On DO network config, I verified I have 1 A record (pointing to my droplet), and 3 NS records (ns1-ns3).

Any ideas what can possibly be causing 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
1 answer

Hey friend!

I did some digging on this for you and I found that the parent TLD for the .club domain is not returning any results for You should contact NameCheap about this, as they are the only ones who can push changes upstream to the parent TLD on your behalf.

To show my work, I first checked to find the DNS servers for the .club TLD by running this:

[root@gateway] ~ # dig NS club +short

Then I queried one of those DNS servers directly and received no result:

[root@gateway] ~ # dig NS
;                   IN      NS

club.                   60      IN      SOA 1538374201 900 900 604800 60


  • Thank you so much for looking into this Jarland. I’ve reached out to Namecheap and they requested to reach out to via email to see why my domain was put on hold. This is ridiculous. Had this been one of my business websites, I’d be losing money. Idk if this is common with .club domains, but I’m really hesitant on going with those in the future. Never had any issues with domains.

    Once again, thanks !