0
I set up a Apache2 on a new Solaris machine on my company's internal (firewalled) network and configured it for name-based virtual hosts.
We don't yet have a domain for the new machine, so I created my own, "lsiden.net", and named the host something like "myhost.lsiden.net" in the httpd.conf <VirtualHost> directive.
Since no such domain is registered, I created the entry "w.x.y.z myhost.lsiden.net" in my /etc/hosts file. (I will delete it when we get a real domain name.)
I can ping myhost.lsiden.net but if I type it in either IE7 or Google Chrome 10, it won't resolve. Is there something that is preventing each browser from looking in the /etc/hosts file?
(In order to access my company's VPN, I have to use the machine that they configured for me which was provisioned with Windows XP. So /etc/hosts is actually something like c:\Windows\system32\drivers\etc\hosts, but that shouldn't matter.)
Check your /etc/nsswitch.conf and /etc/resolv.conf. Both control how DNS resolution works on the local machine. – None – 2011-03-24T22:25:41.597
2You use IE/Chrome on the Solaris? – M'vy – 2011-03-24T22:27:15.253
No. A Solaris machine hosts the site. I must use IE or Chrome (or FF) on a Win-XP computer to access the site because of VPN and company IT restrictions. – Lawrence I. Siden – 2011-03-25T01:01:08.153
On Windows, there is no nsswitch.conf or resolv.conf. Is there some equivalent that controls whether or not DNS will look first in .../etc/hosts? – Lawrence I. Siden – 2011-03-25T01:05:15.467
I found this post that suggested that I restart the DNS cache on Windows. Tried it. Can ping it with my URI, but still can't reach it from the browser. Rats!@
– Lawrence I. Siden – 2011-03-25T01:25:56.083