Mark, You understand the problem. That should work but I've been reluctant to do that. The goal is to maintain a configuration in development that mirrors production. I test all configuration changes on the LAN then push the file(s) into production. Jeff > Hi, > > Sorry if I have the wrong end of the stick, but why don't you just do.... > > NameVirtualHost 10.37.74.24:80 > > in your httpd.conf > > and then set your virtualhost to that NameVirtualHost. > > <VirtualHost 10.37.74.24:80> > ServerName www.myserver.com > > > Again sorry if I've misunderstood your problem. > > Regards, > > Mark. > > > > > > > > > > > > On 11/07/07, Jeff Fulmer <jeff@xxxxxxxxxx> wrote: >> >> -----Original Message----- >> >> From: Jeff Fulmer [mailto:jeff@xxxxxxxxxx] >> >> Sent: Tuesday, July 10, 2007 2:56 PM >> >> To: users@xxxxxxxxxxxxxxxx >> >> Subject: apache hostname resolution (strange problem) >> >> >> >> I have the oddest situation. I have a test server on the LAN. >> >> I added a >> >> host entry for www.myserver.com (actual name changed to protect the >> >> innocent). I can ping www.myserver.com and my resolved >> >> address matches the >> >> host entry. Life is grand, no? >> >> >> >> /usr/sbin/ping www.myserver.com >> >> PING www.myserver.com: 64 byte packets >> >> 64 bytes from 10.37.74.24: icmp_seq=0. time=0. ms >> >> >> >> I have apache configured with a virtual host for >> >> www.myserver.com. Watch >> >> what happens when I check my virtual hosts with httpd -S. I >> >> get the PUBLIC >> >> internet address for www.myserver.com: >> > >> > What exactly is your problem? What address do you expect to get? >> > >> > Your posting is confusing because it's not clear whether your munged >> > domain names are supposed to be internal LAN names or public domain >> > names... >> > >> >> I expect it to be 10.37.74.24. It can't bind a virtual host to an >> address >> that's not on the server. Here's the output of httpd -S >> >> lccas243$ bin/httpd -S >> VirtualHost configuration: >> 64.157.185.199:80 www.myserver.com >> (/usr/local/httpd/conf/vhosts/80_myserver.com:5) >> wildcard NameVirtualHosts and _default_ servers: >> *:443 is a NameVirtualHost >> default server www.myserver.com >> (/usr/local/httpd/conf/vhosts/443_myserver.com:4) >> port 443 namevhost www.myserver.com >> (/usr/local/httpd/conf/vhosts/443_myserver.com:4) >> *:80 is a NameVirtualHost >> >> On the server itself, www.myserver.com resolves to 10.37.74.24 which is >> the address I have in the /etc/hosts file. But apache is resolving it >> based on it's DNS entry. It does this even when I turn DNS off! >> >> Jeff >> >> >> --------------------------------------------------------------------- >> The official User-To-User support forum of the Apache HTTP Server >> Project. >> See <URL:http://httpd.apache.org/userslist.html> for more info. >> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx >> " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx >> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx >> >> > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|