httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Fulmer" <>
Subject RE: [users@httpd] apache hostname resolution (strange problem)
Date Wed, 11 Jul 2007 14:55:40 GMT
>> -----Original Message-----
>> From: Jeff Fulmer []
>> Sent: Tuesday, July 10, 2007 2:56 PM
>> To:
>> Subject: [users@httpd] apache hostname resolution (strange problem)
>> I have the oddest situation. I have a test server on the LAN.
>> I added a
>> host entry for (actual name changed to protect the
>> innocent). I can ping and my resolved
>> address matches the
>> host entry. Life is grand, no?
>> /usr/sbin/ping
>> PING 64 byte packets
>> 64 bytes from icmp_seq=0. time=0. ms
>> I have apache configured with a virtual host for
>> Watch
>> what happens when I check my virtual hosts with httpd -S. I
>> get the PUBLIC
>> internet address for
> 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 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:
wildcard NameVirtualHosts and _default_ servers:
*:443  is a NameVirtualHost
         default server
         port 443 namevhost
*:80                   is a NameVirtualHost

On the server itself, resolves to 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!


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message