Addressed to: "Scott Rothgaber" <[EMAIL PROTECTED]>
[EMAIL PROTECTED]
** Reply to note from "Scott Rothgaber" <[EMAIL PROTECTED]> Mon, 26 Feb 2001 09:45:42
-0500
>
> PHP 4.0.4 pl1, Apache 1.3.17, BSD/OS 4.1 pl37
>
> Good Morning!
>
> Please forgive me if this has been covered ad nauseum, but I
> have searched high and low for an answer with no luck.
>
> After building PHP as a module, following the online
> instructions, Apache complained that it could not resolve
> hostnames. I got around this by using IP's in httpd.conf and
> making wusage do the lookups.
>
> Is there a fix for this or is it an unpleasant side effect that
> we must accept and deal with?
The official word on the Apache config files is that you _should_ use IP
addresses rather than host names.
That said, I don't do it. I find the host names more understandable
when I am working on the file. The problem is you MUST make sure DNS
or /etc/hosts name resolution is available BEFORE you start the web
server.
The first thing to try is get a list of the host names that fail and do
a nslookup to make sure you can resolve them. You may have bigger
problems with DNS.
If the problem happens only when you boot the computer, make sure you
start networking ans named long before you try to start the web server.
A way to side step the entire DNS issue is to list each of your web IP
addresses in /etc/hosts, and make sure that /etc/resolv.conf looks in
that file before it goes out to DNS. Even if you do this you need to
find out why the host names can not be resolved. If the master DNS
server is setup wrong, no one will be able to see the site.
Rick Widmer
Internet Marketing Specialists
http://www.developersdesk.com
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
