Edward Ruggeri wrote:
(Of course, my system hostname (in /etc/hostname) is not fully qualified.)
On 26.09.09 12:49, Stephen wrote:
Your hostname, should have an entry in /etc/hosts
127.0.0.1 hostname
Then Apache is happy and you are fine.
no, It should be at lease
127.0.0.1 localhost
Edward Ruggeri wrote:
On Sat, Sep 26, 2009 at 6:21 PM, Norman Peelman npeel...@cfl.rr.com wrote:
Apache (linux/windows) will check the 'hosts' file first and then do DNS
lookups when no matches are found. I don't understand why your not worried
about why it needs it but you are worried about
On Sat, Sep 26, 2009 at 12:49 PM, Stephen stephe...@rogers.com wrote:
Edward Ruggeri wrote:
(Of course, my system hostname (in /etc/hostname) is not fully qualified.)
Your hostname, should have an entry in /etc/hosts
127.0.0.1 hostname
Then Apache is happy and you are fine.
Thanks, but,
Hi,
I am running Apache 2.2.9 on Debian 5.0.3. Everything seems to work
nicely, but I'm worried about this quote from Issues Regarding DNS
and Apache in the 2.0 documentation:
The addition of name-based virtual host support in Apache 1.1
requires Apache to know the IP address(es) of the host
Edward Ruggeri wrote:
(Of course, my system hostname (in /etc/hostname) is not fully qualified.)
Your hostname, should have an entry in /etc/hosts
127.0.0.1 hostname
Then Apache is happy and you are fine.
Stephen
-
The
Edward Ruggeri wrote:
Hi,
I am running Apache 2.2.9 on Debian 5.0.3. Everything seems to work
nicely, but I'm worried about this quote from Issues Regarding DNS
and Apache in the 2.0 documentation:
The addition of name-based virtual host support in Apache 1.1
requires Apache to know the IP
Edward Ruggeri wrote:
On Sat, Sep 26, 2009 at 12:49 PM, Stephen stephe...@rogers.com wrote:
Edward Ruggeri wrote:
(Of course, my system hostname (in /etc/hostname) is not fully qualified.)
Your hostname, should have an entry in /etc/hosts
127.0.0.1 hostname
Then Apache is
