Hi there! I'm using SuSE 8.0, now with SuSEfirewall2. It serves as a Router, File-, eMail- and Webserver. No problem so far. I use a DynDNS dynamic host adress (someone.ath.cx) and DSL - still no problem. Only when I try to connect (e.g. with a webbrowser) from inside the network to the dynamic hostname, there is a problem: nothing happens, no pages are shown. If i use the internal name of the server (linux1.net.intern), it works. If i try to ping the dynamic host name (someone.ath.cx), i get errors. On the server itself, this works. I guess, there is something that must be configured inside the firewall... Or is there a chance to use the local DNS to avoid the routing of the dynamic adress outside the server? Yours, Wolfgang
Wolfgang Eul wrote:
Only when I try to connect (e.g. with a webbrowser) from inside the network to the dynamic hostname, there is a problem: nothing happens On the server itself, this works. I guess, there is something that must be configured inside the firewall...
See Togan excellent SuSEfirewall2 FAQ available at http://sourceforge.net/project/showfiles.php?group_id=42064&release_id=127876 and follow his advices at Chapter 8.1.6
Or is there a chance to use the local DNS to avoid the routing of the dynamic adress outside the server?
Yes, I do that. My router runs a BIND daemon, which answers questions about local.dyndns.org from a local zone file. Peter
participants (2)
-
Peter Wiersig
-
Wolfgang Eul