I use Apache2 on Ubuntu Karmic (9.10) and have LAMP set up. I can access my host from http://palz2015.ath.cx as well as 10.0.0.12 (internal IP) on any LAN computer (additionally localhost and 127.0.0.1 from the computer itself). But when I try to connect from another computer, I get a 404 gateway timeout. This is the same with my WAMP Windows 7 partition. I use US AT&T and have a Netgear WGR614v9 router. Can someone help me?

Please correct my unorthodox posting if applicable

Please see this sticky which covers port forwarding and testing. From what you've posted I'm guessing either you haven't configured port forwarding or your ISP blocks port 80/TCP inbound.

Well I thought about that. Can you elaborate on how to change the port and update the host on a netgear panel?? I've changed my HTTP port forwarding (server=10.0.0.12) to use port 8090 and now I cannot access my host. Besides IP on the lan, of course.

You also need to configure your web server to listen on port 8090 - it's documentation should explain how to do that.

As there are many different Netgear models I can't provide generic instructions. If you can provide the model and revision, and a link to a PDF manual, I'll tell you what pages provide the information you need.

OK, well I have a WGR614v9. I have 3 port forwards:
HTTP: 10.0.0.12 Port 80 - 90 for XAMPP
PPTP: 10.0.0.12 Port 1723 - 1723 for VPN that I don't really use
FTP: 10.0.0.12 Port 20 - 21 for FileZilla server

...and I now have XAMPP on windows and it works beastily (great). I still can no longer connect to my hostname, palz2015.ath.cx

How can I modify this host to use my *dynamic* IP with port 8090? I tried to use WebHop, but I do not understand that (noobish, right?)

Can you still connect to 10.0.0.12 on port 80? If so then it's probably either your ISP blocking port 80 or you're not running an update client (and your WAN IP has changed).

As far as using port 8090 goes - all you have to do is forward it to a device and port that has a service listening on it. Your hostname only ever resolves to your WAN IP - what port you use is, as always, down to the protocol.

Think of it like a telephone exchange. Your hostname reaches the exchange, but you still need to know who you want to speak to (the port) to reach a person (service).

I don't know if Google Chrome caches favicons, but I have my XAMPP favicon and the This link appears to be broken. message. So no, I can only access my server 2 ways:
http://localhost:8090 and
http://10.0.0.12:8090

Basically, how to I take my WAN IP in my host and get it so the user doesn't need to enter :8090?

You can utilize a WebHop redirection.

Ok, done:
palz2015.ath.cx is for M.Y.I.P
palz2016.ath.cx is for palz2015.ath.cx:8090.

The prob with this is from my machine at least, It redirects, but it still cannot access. Can you try?

http://palz2016.ath.cx

It seems like you haven't forwarded 8090/TCP to 10.0.0.12, or you have a firewall on that host.