• Need Help W Server, Outside to Inside routing from eternal Subdomain

    From SwiTcH@1:0/0 to All on Thu Nov 14 02:14:55 2013
    I have an external SUB.DOMAIN.XXX that I have setup DNS to My.Eternal.Network.IP address and i need it to go to My.Local.Network.Address on my LAN ......

    I am new at this but need to get it up by the AM... Can anyone help? I can get into my router and change all settings just not sure if I need NAT or PORT FORWARDING set up to route traffic to the internal server.. @ My.Local.Network.Address

    Thanks in advance for the help!! Both my host and my service provider threw their hands up on helping out :)

    SwiTcH

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: The Kofo System II BBS telnet://fido2.kofobb
  • From David Brown@1:0/0 to All on Thu Nov 14 20:41:45 2013
    Subject: Re: Need Help W Server, Outside to Inside routing from eternal Subdomain

    On 14/11/13 03:14, SwiTcH wrote:
    I have an external SUB.DOMAIN.XXX that I have setup DNS to My.Eternal.Network.IP address and i need it to go to
    My.Local.Network.Address on my LAN ......

    I am new at this but need to get it up by the AM... Can anyone help?
    I can get into my router and change all settings just not sure if I
    need NAT or PORT FORWARDING set up to route traffic to the internal
    server.. @ My.Local.Network.Address

    Thanks in advance for the help!! Both my host and my service provider
    threw their hands up on helping out :)

    SwiTcH


    Port forwarding is what you want if you are talking about a few ports
    (such as port 80 for http, port 443 for https, 22 for ssh, etc.). You
    set your router to forward external traffic on these ports towards your address on the LAN.

    If you want /everything/ forwarded (which is usually /not/ a good idea), routers often allow that with terms such as "DMZ" or "virtual server" - basically an IP address to receive all traffic that is not explicitly forwarded somewhere else.

    Make sure your LAN machine has a fixed IP address on the network.

    Make sure your firewall/router does not block the traffic (for some
    routers, you configure the port forward in one place, and "open" the
    port in another).

    Enable logging on your firewall/router, especially while testing, and
    check the log regularly.

    Make sure your external IP is fixed, or use a dynamic DNS service.


    mvh.,

    David


    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: The Kofo System II BBS telnet://fido2.kofobb