Internal/external Web Site Acces

I know that this question might sound trivila and I know that I used to resolve this issue in the past under redhat. I just installed OpenSuSE 10.3, setup firewall and HTTP server.

The issues that I have is I can access my web site from outside my home network, but I cannot access it from the inside my home network. To me this sound like a name resolution but I might be wrong. What might be the problem?

Thanks!

When you think it has something to do with name resolution the obvious test is trying the IP address.

In my internal network if I point to the internal IP address 192.168.x.x I am getting to the site. If I try to point to the external IP address, I am going nowhere and eventually it times out...If I trace it, and look at the logs, I can see request going to the router, forwarded to the internal IP address of the SuSE server and getting lost there... The firewall log shows the correct request being accepted.

Again, everything is great if I access it from the outside my home network.

When I understand rightly:
1) from the internet to your external IP address (router) is forwarded to your internal IP address and goes OK.
2) from internal to your internal IP address goes OK.
3) from internal to your external IP address (router from outside) is forwarded to your internal IP address and gets lost (that means it is not even rejected by your firewall or Apache because it simply does not arrive).

I do not see why this is not working, but imho it has nothing to do with name resolving.

Hope more people are reading this, I am stuck for the moment.

When I understand rightly:
1) from the internet to your external IP address (router) is forwarded to your internal IP address and goes OK.
2) from internal to your internal IP address goes OK.
3) from internal to your external IP address (router from outside) is forwarded to your internal IP address and gets lost (that means it is not even rejected by your firewall or Apache because it simply does not arrive).

I do not see why this is not working, but imho it has nothing to do with name resolving.

Hope more people are reading this, I am stuck for the moment.
[/b]

You got it correct! In my opinion it should work too...

You got it correct! In my opinion it should work too...
[/b]

External requests for port 80 (website) traffic will be port forwarded by the router to the settings on the router.
Internal requests are seen as being internal and not from outside despite the fact that you're using a full web address since the router will find the shortest route for traffic.
Since the router itself handles web traffic for its own interface internally, your call to www.yourdomain.whatever is being picked up by the router rather than forwarded to the webserver.

Solutions
Use direct IP address rather than dns routing while on the LAN side.
If it'll let you, change the port for the router's web interface from 80 to something else and set up an internal port forward rule to forward 80 to the webserver.
Get a better router.

OK. Most of the times the solution is closer then you think...

I have a Linksys router. I had the Filter NAT Redirection box ckecked...which means that no matter what your internal request are going to be kept internal...simply unchecked the box and everything works fine...

OK. Most of the times the solution is closer then you think...

I have a Linksys router. I had the Filter NAT Redirection box ckecked...which means that no matter what your internal request are going to be kept internal...simply unchecked the box and everything works fine...
[/b]

Which is effectively the second option I suggested, since it forces the rule for the wan to apply also to the lan.
Glad you're sorted.