cross-posted from: https://lemmy.world/post/14180956

Hello all you lovely people!

I’m trying to figure out if I can port forward to different servers based on the destination domain.

I have a domain with a wildcard cert and I’d like to be able to route all traffic headed towards “1.domain.com” to a server I’m calling “1”. I’d still like traffic headed to domain.com to go to where it’s currently going, we can call this server “0”, and to be able to have a 2.domain.com or 3 or 4 in the future.

I thought that having a port forward rule with: interface: WAN Protocol: any source: any destination: a url alias including 1.domain.com redirect target ip: local ip

Would work, but it doesn’t seem to. Any tips?

  • Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    2
    ·
    9 months ago

    Okay if I’m reading this it’s because you want to ssh into two or more servers from the outside. I get the goal, but I’ll tell you it’s not great security.

    What I personally have used and recommend is that you set up a bastion ssh server. A public ssh server that is exposed, preferably on another port, that is heavily locked down. Once you ssh into the bastion, then you’re in the network and can ssh anywhere using your internal DNS.

    The added security benefit is that if someone does get into that box, they still need to learn your network topography. Not security, but bastion doesn’t do anything, so they’re not immediately into a core system.

    Added bonus if you do a honepot on 22 and bastion on a different port.