-Original Message-
> From: Deephay [mailto:[EMAIL PROTECTED]
> Sent: Saturday, July 28, 2007 1:35 AM
> To: users@httpd.apache.org
> Subject: Re: [EMAIL PROTECTED] determine FQDN problem
>
> On 7/28/07, Graham Frank <[EMAIL PROTECTED]> wrote:
> > Hey,
> >
&
Business Bureau
-Original Message-
From: Deephay [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 28, 2007 1:35 AM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] determine FQDN problem
On 7/28/07, Graham Frank <[EMAIL PROTECTED]> wrote:
> Hey,
>
> That's mo
m: Deephay [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 27, 2007 2:17 PM
> To: users@httpd.apache.org
> Subject: Re: [EMAIL PROTECTED] determine FQDN problem
>
> On 7/27/07, Graham Frank <[EMAIL PROTECTED]> wrote:
> > Basically, it's looking at the ServerName directi
er
Ph: (608) 359-1593
Member of the Better Business Bureau
-Original Message-
From: Deephay [mailto:[EMAIL PROTECTED]
Sent: Friday, July 27, 2007 2:17 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] determine FQDN problem
On 7/27/07, Graham Frank <[EMAIL PROTECTED]>
08) 359-1593
> Member of the Better Business Bureau
>
> -Original Message-
>
> From: Deephay <[EMAIL PROTECTED]>
> Subj: Re: [EMAIL PROTECTED] determine FQDN problem
> Date: Fri Jul 27, 2007 2:36 am
> Size: 2K
> To: users@httpd.apache.org
>
> On 7/27/07
--- Graham Frank <[EMAIL PROTECTED]> wrote:
> 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.
I'm getting a similar message right now, httpd can't
resolve domain name from ypbind.
I haven't fixed the
Graham Frank
Neoservers, LLC - Founder and Owner
Ph: (608) 359-1593
Member of the Better Business Bureau
-Original Message-
From: Deephay <[EMAIL PROTECTED]>
Subj: Re: [EMAIL PROTECTED] determine FQDN problem
Date: Fri Jul 27, 2007 2:36 am
Size: 2K
To: users@httpd.a
On 7/27/07, Graham Frank <[EMAIL PROTECTED]> 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
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.
Mind you, the reason you get this even tho you specify the DNS in t
