Newbie/wannabe/failing webmaster here...I have a Google VM Debian9 instance running Apache2. For the past few months, i had no domain name, so i faked one using a virtual host (crm.fake_example.com) since i was the only user. I added the IP and my fake address to my local hosts file, and everything worked just fine as I stood up a web-based, open source software application on the VM.
I've now pointed a subdomain (crm.real_example.com) to the IP address of my VM. I've waited a full week for DNS propogation (yes, overkill) and have used MXtoolbox - DNSLookup to verify that the subdomain resolves to the correct IP address. I erased any previous entries to my local hosts file.
Visiting the site from my local machine (or any machine) yields the same error ("ERR_NAME_NOT_RESOLVED").
However, if I edit my local hosts file to include the IP and crm.real_example.com...it works just fine again.
I feel like MXtoolbox proves to me that DNS is working, so the problem must exist on my VM somewhere (can someone verify this thinking?) - but I've checked/re-checked all of the following...
On the Google VM apache2 server:
- /etc/hosts is a clean file (nothing from crm.fake_example.com exists in there any longer)
- /etc/apache/sites-available/mysite.conf has the necessary virtual host info (see below)
- note: I know virtual host is not required for only one site...but i plan to add more so want it working using this
- /etc/apache/sites-enabled/mysite.conf activated via a2ensite
- config.inc.php (a vtigercrm-specific config file) has been reconfigured for crm.real_example.com
<VirtualHost *:80>
ServerAdmin me@real_example.com
ServerName crm.real_example.com
DocumentRoot /var/www/html/crm/
<Directory /var/www/html/crm/>
Options FollowSymlinks
AllowOverride All
Require all granted
</Directory>
ErrorLog /var/log/apache2/crm_error.log
CustomLog /var/log/apache2/crm_access.log combined
</VirtualHost>
I could also list all the things i've done on my local machine like clearing DNScache, cleaning up my hosts file, etc...but the same thing happens from any other machine with no previous successful attempts at hitting this server.
After a full week of looking at the same things over and over...any guidance is appreciated!