I don't think the DNS on your machine is the issue, as you're getting to the panel (which is on the same host) okay.. the issue will be at the server end in how it's listening for the host names.
I think issue is that daemon potentially has run, and new vhosts file written, but daemon failed to reload/restart apache2 service, so changes aren't yet loaded in to the apache runtime environment. Try (as standard user) "sudo /etc/init.d/httpd restart" [enter] or (as root user) just "/etc/init.d/httpd restart" [enter] and see if that doesn't fix it.
I've had this happen to me on Windows based installations and restarting Apache was my solution. It's not usually a problem on my Ubuntu 12/14 setups though and I couldn't say much for Centos as I don't use it.
I think issue is that daemon potentially has run, and new vhosts file written, but daemon failed to reload/restart apache2 service, so changes aren't yet loaded in to the apache runtime environment. Try (as standard user) "sudo /etc/init.d/httpd restart" [enter] or (as root user) just "/etc/init.d/httpd restart" [enter] and see if that doesn't fix it.
I've had this happen to me on Windows based installations and restarting Apache was my solution. It's not usually a problem on my Ubuntu 12/14 setups though and I couldn't say much for Centos as I don't use it.
