Re: apache dns problem

2002-11-20 Thread Jake Colman
SC> Edit your httpd.conf file and change the "ServerName" directive to SC> the FQDN that you want apache to annonuce itself as. Works for me. I replaced ServerName firewall.jnchome.com with Servername thecolmans.homeip.net and restarted the server. Even with this change, I must

RE: apache dns problem

2002-11-19 Thread Cowles, Steve
> -Original Message- > From: Jake Colman > Sent: Tuesday, November 19, 2002 3:59 PM > Subject: apache dns problem > > My server's internal name is firewall.jnchome.com. This is a > bogus dns name that resolves only internally. > > I use dyndns.org to map

Re: apache dns problem

2002-11-19 Thread Anthony E. Greene
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19-Nov-2002/16:59 -0500, Jake Colman <[EMAIL PROTECTED]> wrote: > >My server's internal name is firewall.jnchome.com. This is a bogus dns name >that resolves only internally. > >I use dyndns.org to map a public dns name to my dynamic IP address. T

RE: apache dns problem

2002-11-19 Thread Cameron . Davidson
st > Subject: apache dns problem > > > > My server's internal name is firewall.jnchome.com. This is a > bogus dns name that resolves only internally. > > I use dyndns.org to map a public dns name to my dynamic IP > address. The URL "http://thecolmans.homeip.net

apache dns problem

2002-11-19 Thread Jake Colman
My server's internal name is firewall.jnchome.com. This is a bogus dns name that resolves only internally. I use dyndns.org to map a public dns name to my dynamic IP address. The URL "http://thecolmans.homeip.net:8081"; resolves to my web server. If someone enters this URL they get my apache t