Basically, it's looking at the ServerName directive and it isn't a FQDN. I've had this issue before ... trying to think of how I solved it. Mind sharing with us the format of the hostname you set for ServerName? Trying to dig for some more info. ------------------------------------- Graham Frank Neoservers, LLC - Founder and Owner Ph: (608) 359-1593 Member of the Better Business Bureau -----Original Message----- From: Deephay <tudoxxx@xxxxxxxxx> Subj: Re: determine FQDN problem Date: Fri Jul 27, 2007 2:36 am Size: 2K To: users@xxxxxxxxxxxxxxxx On 7/27/07, Graham Frank <gfrank@xxxxxxxxxxxxxx> wrote: > It sounds like Apache just can't resolve the hostname. One thing you could > do is edit the /etc/hosts file and add "127.0.0.1 hostname.com". Since > resolving a hostname will check /etc/hosts first, this should eliminate the > issue. thanks for the explanation. I have the hostname in the /etc/hosts, but the situation persists. Is it possible that apache try to match my ppp0 ip address and failed? I do not know the whole procedure. Cheers. > > Mind you, the reason you get this even tho you specify the DNS in the > virtual host config is because Apache is processing both the Apache config > values for ServerName AND the Virtual Host config values for ServerName. but I do not have any other ServerName except in my vitual host config files. > > ---- > Graham Frank > Neoservers LLC - Founder and Owner > Ph: (608) 359-1593 > Member of the Better Business Bureau --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|