My Domain

[mrmister1]

After getting a good amount of my website complete, I finally tested from another computer, not on my network. Up until that time, I had been testing it on computers on my home network. When I tested it from another computer not on the network, it didn't work. Then I tested the ftp server and it worked fine, except when I tried to open a file. What could be wrong. Try it: http://www.mrmistr.com. The domain name is forwarded to http://mrmistr.dnsalias.com, since it is on a router.

Thanks in advance.

[homer15]

i can't get the second one to work. does it work on other machines as well? are you sure the registrar is pointing to the correct nameservers?

[mrmister1]

You couldn't get either to work? I tried it using the IP address also, and it didn't work either. Could it be a problem with the router. I use a linksys, so I went to the port forwarding page and made sure that all http requests are forwarded to the server as well as ftp requests. Is that right?

Again...it works on local machines on the lan, but not outside.

[homer15]

well, the ip address i got for it (64.202.167.129) takes me straight to godaddy.com where it says your domain is parked. i don't think this is a router problem, i think it's a numbers problem. somewhere along the line, somebody has the wrong numbers or nameservers in their system.

what exactly are you doing with godaddy?

[mairving]

If you do a traceroute (tracert from the windows cmd), the second domain resolves to an Optimum Online address block, which I assume is your ISP. I would suspect that your ISP probably is blocking port 80 so people don't put web servers up. A traceroute to the first domain times out, probably because it can't locate the second domain.

[mrmister1]

So is there anything I can do about it, or am I pretty much screwed?

[mattg2k4]

You could host it on another port, then people would have to put (colon)portnumber after the address. A common port used for this pupose is 81.

Or you could get third part hosting, it's fairly inexpensive.

[mrmister1]

How and where would I switch it on the server, so it goes through port 81?

Thanks again.

[mattg2k4]

It depends on your particular server software, and you may have to check whether your software has that capability. I know apache does, but thats the only http server I've ever used.

You also have to go into your router and forwards port 81, or whatever port you decided on to your server's local LAN IP address.

[mrmister1]

Well I'm using AppServ, which is pretty close to Apache...Would it be the same on both. Where would it be on Apache, and I'll check on AppServ.

[mattg2k4]

Apache has a line in the httpd.conf file "Listen 80", which you can add to or change to have apache listen on any port. If you open AppServ's config file (assuming it's plain text) you can just search for "80" and the will probably take you to the listing of ports its listening on.