Glen Vickers wrote:
Glen Vickers wrote:
K I figured out whats going on with my virtual hosts. I have to have 3
because of the differences. But I noticed that if I go sillumutah.com
or sillumutah.net it works fine..
If I put the WWW in front or any other prefix it bombs to the default.
So
Glen Vickers wrote:
>
> K I figured out whats going on with my virtual hosts. I have to have 3
> because of the differences. But I noticed that if I go sillumutah.com
> or sillumutah.net it works fine..
>
> If I put the WWW in front or any other prefix it bombs to the default.
> So my guess is i
Glen Vickers wrote:
K I figured out whats going on with my virtual hosts. I have to have 3
because of the differences. But I noticed that if I go sillumutah.com
or sillumutah.net it works fine….
If I put the WWW in front or any other prefix it bombs to the default.
So my guess is its my vir
Glen Vickers wrote:
K I figured out whats going on with my virtual hosts. I have to have 3
because of the differences. But I noticed that if I go sillumutah.com
or sillumutah.net it works fine….
If I put the WWW in front or any other prefix it bombs to the default.
So my guess is its my vir
http://www.debian-administration.org/articles/358
This article might be of help to you
On May 14, 2007, at 6:35 PM, Glen Vickers wrote:
K I figured out whats going on with my virtual hosts. I have to have 3
because of the differences. But I noticed that if I go sillumutah.com or
sill
http://www.debian-administration.org/articles/358
This article might be of help to you
On May 14, 2007, at 6:35 PM, Glen Vickers wrote:
K I figured out whats going on with my virtual hosts. I have to
have 3 because of the differences. But I noticed that if I go
sillumutah.com or sillumuta
K I figured out whats going on with my virtual hosts. I have to have 3
because of the differences. But I noticed that if I go sillumutah.com or
sillumutah.net it works fine..
If I put the WWW in front or any other prefix it bombs to the default. So
my guess is its my virtual server config
I don't get it. Maybe you should post your problem on
an Suse list.
- Original Message -
From: "john" <[EMAIL PROTECTED]>
To:
Sent: Thursday, January 11, 2007 10:03 AM
Subject: RE: [EMAIL PROTECTED] Name Resolution error
> My system is able to resolve all
My system is able to resolve all the hostnames.
The problem occurs during the boot.
-Original Message-
From: Krist van Besien [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 11, 2007 3:28 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Name Resolution error
On 1/11/07
On 1/11/07, john <[EMAIL PROTECTED]> wrote:
My config is
...
ServerAdmin root@ Domainname1
ServerName Domainname1
Is your server able to resolve this name? The problem might be that
apache is not able to find out what IP adress this Virtual Host needs
to be atached too.
Krist
--
[E
My config is
...
ServerAdmin root@ Domainname1
ServerName Domainname1
.
-Original Message-
From: Krist van Besien [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 11, 2007 2:48 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Name Resolution error
On 1
On 1/11/07, john <[EMAIL PROTECTED]> wrote:
Well, I did what you mentioned but the problem remains
Cannot resolve the virtual hosts.
When you say that "Domainname1" is the name of one of your virtual
hosts, what do you exaclty mean by that? Can you post us part of your
actual config?
Kr
Well, I did what you mentioned but the problem remains
Cannot resolve the virtual hosts.
Any other ideas?
_
From: Jonathan Mangin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 10, 2007 11:20 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Name Resolution
: john
To: users@httpd.apache.org
Sent: Wednesday, January 10, 2007 11:45 AM
Subject: RE: [EMAIL PROTECTED] Name Resolution error
The script is /etc/rc.d/rc3.d/S11apache2 -> ../apache2
I feel that the priority of the apache's beginning was unexpectedly
om: john <mailto:[EMAIL PROTECTED]>
To: users@httpd.apache.org
Sent: Wednesday, January 10, 2007 8:55 AM
Subject: RE: [EMAIL PROTECTED] Name Resolution error
I totally agree with you.
My system is an opensuse 10.1 and I didn't have any problem until the last
update thro
che.org
Sent: Wednesday, January 10, 2007 8:55 AM
Subject: RE: [EMAIL PROTECTED] Name Resolution error
I totally agree with you.
My system is an opensuse 10.1 and I didn't have any problem until the last
update through YOU.
Do you experience
e.org
Subject: Re: [EMAIL PROTECTED] Name Resolution error
Sorry about that.
- Original Message -
From: john <mailto:[EMAIL PROTECTED]>
To: users@httpd.apache.org
Sent: Tuesday, January 09, 2007 2:37 AM
Subject: RE: [EMAIL PROTECTED] Name Resolution error
HostnameLoo
Sorry about that.
- Original Message -
From: john
To: users@httpd.apache.org
Sent: Tuesday, January 09, 2007 2:37 AM
Subject: RE: [EMAIL PROTECTED] Name Resolution error
HostnameLookups is for logging.
I have other systems with many virtual hosts and there is no
- Original Message -
From: john
To: users@httpd.apache.org
Sent: Tuesday, January 09, 2007 2:37 AM
Subject: RE: [EMAIL PROTECTED] Name Resolution error
HostnameLookups is for logging.
I have other systems with many virtual hosts and there is no problem at all
,
everything works fine.
_
From: joseph c [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 09, 2007 7:48 AM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Name Resolution error
how about the value of the "HostnameLookups", it should set to "Off"
On
how about the value of the "HostnameLookups", it should set to "Off"
On 1/9/07, john <[EMAIL PROTECTED]> wrote:
Hi all
I have installed apache 2.2.3
Apache starts automatically, so there is an error
[Mon Jan 08 20:11:27 2007] [error] (EAI 3)Temporary failure in name
resolution: Could not res
Hi all
I have installed apache 2.2.3
Apache starts automatically, so there is an error
[Mon Jan 08 20:11:27 2007] [error] (EAI 3)Temporary failure in name
resolution: Could not resolve host name DomainName1 -- ignoring!
[Mon Jan 08 20:11:27 2007] [error] (EAI 3)Temporary failure in name
resoluti
22 matches
Mail list logo
