[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?