NS or router problem?

[finger]

Recently upgraded to Apache2 and suse9.1 pro at home. The box is behind a linksys dsl router.
I can hit the page from within my lan, but not from outside. I've forwarded port 80 to the internal address of my server but I still get a '500 error' when I try to hit it from outside my lan.
From work, I've tried to resolve the external IP via http: as well and no dice. When I ping http://IP.address. I get unknown host.

Is this a nameservice problem? I recently switched to zoneedit, but I did so before I did my upgrade to apache2. It was working fine up until I upgraded. The A record is correct for my site.

I really think this is related to the router, but I can't prove it. The ports are forwarded in the admin page, but I can't ping, can't resolve http or IP externally- (inside my lan I can resolve no problem).

I also checked netstat and /etc/services both show port 80 is up and running- this is proved since I can get to the page internally.

I'm stumped, have I overlooked something?

 

[Xtremist]

Your post is a little confusing to me, but I think? I have the general idea of what you've tried...

"I've tried to resolve the external IP via http: as well and no dice

This meaning you tried to open: http://PUBLIC_IP_HERE/ in a web browser?

I also don't believe you can ping with the protocol attached to the IP. So just try: ping PUBLIC_IP_HERE

Either way though, that doesn't really mean anything anyway. You can have one port/protocol blocked while allowing others, so you could easily ping and not access HTTP/80 and vice-versa.

If you're trying to access the site via the raw IP and not a hostname, you can forget about it being a nameserver issue. Which is what you should cancel out first anyway in your case. Make sure you're really using the REAL public IP for your router, not the internal router IP (not like a 10.x.x.x, 192.168.x.x, and can't remember the class c range). If you're trying to access it via the private router IP, it's not going to work outside your network no matter WHAT you do.

If you really are using a public, routable, IP and not the private IP or hostname, to test this out, it's most likely an issue with your router. You could try and see if your router will forward EVERYTHING (temporarily) to that internal machine and then see if it works. Sorry I can't offer more, I honestly found your post somewhat confusing.

 

[finger]

sorry 'bout the confusion... I'll try again

Trying to hit my page from work

http://63.198.xxx.xxx -no go
http://mydomain.com -no go
ping 63.198.xxx.xxx -no go


Trying to hit my page from internal network

http://63.198.xxx.xxx - page displays normally
http://localhost - page displays normally
http://172.16.1.x - page displays normally
ping 63.198.xxx.xxx - ping response is good


It's the router right?

 

[Xtremist]

Most likely the router yes. Just remember though that HTTP and PING don't 'both' have to work so spending a lot of time trying to get PING might not solve your real problem.

Having said that, the only thing I can really think of besides the router (which you'll probably have to mess with yourself) is if there's some sort of firewall between the server and your router (or on the server itself). It could be allowing any connections internally, but denying otherwise. It's a long-shot, but that's the only other thing I can think of...