On Sat, 2002-12-14 at 21:40, Rick Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bret Hughes wrote:
>
> | probably would not hurt to replace some.domain.here in the servernae
> | directive too. This will fix directory accesses to dirs not ending in /
> | I belive.
> |
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bret Hughes wrote:
| probably would not hurt to replace some.domain.here in the servernae
| directive too. This will fix directory accesses to dirs not ending in /
| I belive.
|
The problem w/ using a hostname is that Apache must resolve that name
e
On Sat, 2002-12-14 at 11:53, Rick Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Søren Neigaard wrote:
> | I keep getting this error message when I start Apache:
> |
> | [Sat Dec 14 13:34:43 2002] [error] (22002)Name or service not known:
> Failed to resolve server name for 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Søren Neigaard wrote:
| I keep getting this error message when I start Apache:
|
| [Sat Dec 14 13:34:43 2002] [error] (22002)Name or service not known:
Failed to resolve server name for 192.168.1.5 (check DNS) -- or specify
an explicit ServerName
|
| B
I keep getting this error message when I start Apache:
[Sat Dec 14 13:34:43 2002] [error] (22002)Name or service not known: Failed to resolve
server name for 192.168.1.5 (check DNS) -- or specify an explicit ServerName
But everything seems to work fine. What's the problem here, the IP
"192.168.1
