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 any similar problem? _____ From: Jonathan Mangin [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 09, 2007 4:56 PM To: users@httpd.apache.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 HostnameLookups is for logging. I have other systems with many virtual hosts and there is no problem at all. Is there any possibility that when apache starts (runlevel 3) cannot resolve the host names. If I shut the apache (having resolution problem) and then just restart it, 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 1/9/07, john <[EMAIL PROTECTED] <mailto:[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 resolve host name DomainName1 -- ignoring! [Mon Jan 08 20:11:27 2007] [error] (EAI 3)Temporary failure in name resolution: Could not resolve host name DomainName2-- ignoring! DomainName1 and DomainName2 are the names for my virtual hosts. After that error I have to reload apache and then everything works fine. ------------------------------------ In /etc/rc3.d I have S99apache2. Doesn't the 99 have to do with the order services are started? I see in Solaris that network services are started in run level 2.
