[deanhills]

First of all - this happened with my paid VPS with HostUS - not my VPS 9.

My primary domain of my HostUS has been running successfully for many months.  No issue before.  I haven't touched any of its info at the domain Registrar.  Name servers for the primary domain are Namecheap name servers that I created from the domain.

So tonight when I tried to access the primary domain of my HostUS VPS, the domain was dead in all browsers.  First thought was that my VPS had gone down, but when I checked my panel at HostUS the VPS was running OK.  I was able to access the VPS through Putty as well and everything looked normal except the domain was dead.  That severely puzzled me.

I then tried my IP instead of my domain, and found I was able to access the domain with my IP.  The domain wasn't working but the IP was working.  Kind'a weird!

Then a little after that - immediately after I had opened a support ticket with HostUS, all of a sudden the domain started working again.  HostUS didn't fix it - like couldn't have responded yet.  It came on by itself.

So what happened? 

I'm using VestaCP - and VestaCP was running OK.  I was able to access VestaCP with the IP but not the primary domain and everything in VestaCP looked normal - i.e. DNS etc.  What I did find though was that for some or other reason Ioncube was missing.  As I wasn't able to get my Softaculous up, whereas previously I had loaded Ioncube.  Could it be an update of VestaCP created a DNS issue?  And caused Ioncube to fail?  Or is there something else?  Any one come across this before?

The Website attached to the domain is a WordPress blog that was installed with my premium Softaculous in VestaCP.

[chanalku91]

Check If Your Domain Is Expired Or Still Active
Also check the DNS on your web server that all settings are correct
Or maybe the DNS server is down
Contact your domain registrar! If this problem cannot be fixed! Most likely they can help you

[deanhills]

Check If Your Domain Is Expired Or Still Active
Also check the DNS on your web server that all settings are correct
Or maybe the DNS server is down
Contact your domain registrar! If this problem cannot be fixed! Most likely they can help you

If you check my OP I did all of that - no need to contact the domain registrar.  Also if you check my OP it's working now.  It was temporarily not working.  Domain is with Namecheap and expires only next year in February.  Name servers were created with Namecheap.  Checked the DNS and everything was OK.  But yes - who knows, maybe the DNS server was down temporarily.

[Littlemaster]

I feel a DNS issue, you got the problem solved already, let us see whether it was a VistaCP issue. Which is your current version?

[xdude]

Probbly some sort of temporary glitch in DNS in your server. I was going to tell you to restart the VPS but then noticed its working now. Support guys might have just restarted the vps even thought they didn't bother to tell you. That's usually the first thing to do. I know in many cases they pretend it just start working again because people start asking all sort of question, like how it as happened, what's wrong, are you guys having problems etc etc.

[chanalku91]

I don't think too much, that restarting the server (VDS / VPS) can solve trivial problems like this!
Thank you with the thread!
It really helped me to improve something trivial

[tryp4vps]

Probbly some sort of temporary glitch in DNS in your server. I was going to tell you to restart the VPS but then noticed its working now. Support guys might have just restarted the vps even thought they didn't bother to tell you........

I do not feel that it should had been fixed by the VPS restart. OP already said the website was fine if he accessed it by IP, just not accessible by the domain.

It does look like it was the issue that the DNS server was not responding during the period.

[deanhills]

Probbly some sort of temporary glitch in DNS in your server. I was going to tell you to restart the VPS but then noticed its working now. Support guys might have just restarted the vps even thought they didn't bother to tell you. That's usually the first thing to do. I know in many cases they pretend it just start working again because people start asking all sort of question, like how it as happened, what's wrong, are you guys having problems etc etc.

True.   Fortunately it's a support ticket that ended almost before it had begun.  First thing I did when I noticed the problem was check my VPS panel.  HostUS has their own BREEZE panel that they designed themselves and it's one of the best I've come across.  One can see at a glance that the VPS is OK - so who knows that would have been the support guys' impression too they probably see the same as I do.  I also checked the DNS with DNS Inspect and that showed no problems either.  I then accessed my VPS through Putty and noticed the IP was working.  And then tried VestaCP and my website with the IP and that worked.  One thing that was odd though was my Ioncube was no longer loaded - it had been installed and working for several months so I could access my Softaculous.  I had to reload Ioncube again. 

I now suspect that during a most recent update of VestaCP that something could have happened.  I'm on automatic updates with VestaCP.  Maybe something happened that caused the DNS to be temporarily down.  

---

I feel a DNS issue, you got the problem solved already, let us see whether it was a VistaCP issue. Which is your current version?

I'm sure you're right.  My thinking is that it could have happened with a VestaCP update.  My Ioncube went down - maybe something else happened too that affected the DNS.  Thankfully temporarily. 

---

Tonight discovered my other VPS - VPS 9 - also got into trouble after the last VestaCP update.  This one is MUCH MUCH worse!  My DNS Named Server got corrupted.  I couldn't restart it.  So looks as though I'll have to reload everything from scratch again.  Darn!  

I tried everything first.  VestaCP has ability in the panel to start/restart Named Server.  That didn't work.  I followed one of the Admin's suggestions step by step, that didn't work.  I then discovered at a CentoS Forum that it must have gotten corrupted.  Only way to save this is to start fresh. Fortunately I have current backups but darn darn and darn again.  Wonder what was in that update to create such a negative effect on my DNS Named Server?