10-03-04 10:50 PM
On 2 Oct 2004 22:38:35 -0700, ThinkTank89 <ThinkTank89@gmail.com> wrote:
> Ill keep it short.
>
> Status:
> Linux (Fedora Core 2) Installed
> -I'm no expert but I know my way around
> Domain = www.lazylair.com registered via GoDaddy.com
> NameServer set as ns1.lazylair.com (if that matters)
Whois says your domain exists, but your DNS is seriously broken:
> host www.lazylair.com
;; connection timed out; no servers could be reached
> dig lazylair.com
; <<>> DiG 9.2.2 <<>> lazylair.com
;; global options: printcmd
;; connection timed out; no servers could be reached
How do you expect anyone to resolve www.lazylair.com if they cannot
resolve ns1.lazylair.com or ns2.lazylair.com? You should either give your
registrar static IPs for your nameservers, have someone other than
yourself resolve the nameservers, or use a dynamic DNS service.
> Port 8080 Forwarded to server comp via router configuration
> Port 8080 unblocked on Computer firewall
Note that you would need to include any non-standard port in the URL like
http://www.lazylair.com:8080/
> Important Fact: Apace version is most likely 2.0 as in the
> configuration file is
> "See <URL...docs-2.0> for ..."
>
> Problem:
> Fresh httpd.conf file ready to edit, what now?
>
> MAIN REQUEST:
> A list of vital things to edit in httd.conf and what values to place
> in them.
> Please be specific, I'm new and examples such as "new.host.name:80"
> seams to not to get the message across.
Why would you put "new.host.name:80" somewhere if using port 8080?
Initially you should not have to do much of anything except bind apache to
port 8080, possibly move default pages to some other name, replaced with
your own, and check for any Allow and Deny directives, to allow public
access. You should also likely set UseCanonicalName off (so redirects
will work properly from intranet or internet).
> Your aid would be much appreciated. E-mail is ThinkTank89@gmail.com
[ Post a follow-up to this message ]
| 
