Vesta Control Panel - Forum

First of all, let me say VestaCP is fantastic!
What I'm having issue with is getting subdomains to resolve, 'be found' despite an almost immediate DNS record appearing on a dig.

I added sub.domain.com as a web domain with DNS support and pointed it to the IP.
The folder is created in the account with the default index that contains "sub.domain.com powered by vesta" and its entry on the DNS domain section appears with all the records.

I can do a dig and there it is with the IP.

Going to the URL results in a "not found" error, so I check using a proxy thinking my ISP has cached it.
The proxy pulls up the root domain page ("domain.com powered by vesta"), as does my mobile internet.
I delete both and confirm that it is gone via ftp (sub.domain.com folder is gone) and mobile browser/proxy.

I added sub.domain without DNS support then put an A record in the DNS for the root domain.com.

"I dig it but my browser don't it!"

What should I be looking for, setting, that I might be missing in my frustration?
Is it outside of Vesta and cached/reused somewhere else (like say by Apache, evn when I delete records in vesta?).

Any help or point in the right/different direction is appreciated.

The full Dig resuts http://tinyurl.com/digresults . its out there, just not on my server according to the webternets browsers

Looks like you have set up dns records correctly. Try to restart web server manually:

RHEL/CentOS Debian/Ubuntu

skid wrote:Looks like you have set up dns records correctly. Try to restart web server manually:

RHEL/CentOS

Code: Select all

service httpd restart
service nginx restart

Debian/Ubuntu

Code: Select all

service apache2 restart
service nginx restart

That did it, skid.
I'd thought I'd done that from the control panel, but in my frustration and *headdesk* I didnt even think to connect ssh and do it the old fashioned way.
Thanks for the outside perspective, it helps when one misses the obvious.

Well, you know it should be done automatically but in some very rare cases process can stuck at some point. We are still working on how to improve restarts. Nice to know you managed it.