Hi everyone!

I’m looking into self-hosting, and I currently have dynamic DNS set up to point to my home IP.

My question: is it worth getting a dedicated IP through a VPN?

I’m pretty technically savvy, but when it comes to networking I lack practical experience. My thought is that pointing my domain to a dedicated IP and routing that traffic to my home IP would be safer - especially if I only allow traffic on certain ports from that IP. Just curious if that idea holds up in practice, or if it’s not worth the effort.

  • peregus@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    I’m curious to know in which case is useful to know the public IP in a firewall rule because I’ve never used it.

    • VelociCatTurd@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      An access rule for instance. To say to allow all traffic or specific types of traffic from a public IP address. This could be if you wanted to allow access to some media server from your friends house or something.

        • VelociCatTurd@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          No fucking shit? In that scenario your friend could use DDNS and you point your access rule to his FQDN to allow access.

          Did you really ask me a billion fucking “why” questions just to come back and fucking what prove me wrong? Is this a good use of your time? I literally thought you were a noobie looking to understand.

          Fuck off.

          • peregus@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 months ago

            Dude, just chill! I didn’t think that your answer made sense in the first place and that’s why I’ve asked why you wrote that sentence. I’m not the one that reply to a comment saying “You’re wrong!”, unless I’m more than sure about what I’m talking, otherwise, and in this case I wasn’t sure and I wanted to know your point. I’m here to give my point of view and also to LEARN from others and this is why I kept asking you what was the need of resolving a DNS in a firewall rule, so that maybe I could start using those rules too. On the other side, if you understood that your answer didn’t make sense, you simply could have just said it and not waste mine and your time. I think that we ALL are here to share idea and knowledge and that NO ONE is perfect, me in the first place!

            • VelociCatTurd@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              edit-2
              2 months ago

              If you really think someone is wrong don’t ask them “why, why, why” incessantly like a toddler, grow a pair of balls and just speak your mind.

              And in this case I meant “your IP” as in, the grand scheme of things “an IP address that you own”, a VPS for instance, not necessarily the destination. Obviously you wouldn’t need to tell a firewall what its own public IP is. Have I clarified my thought to your standards?

              • peregus@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                edit-2
                2 months ago

                You’ve clarified your thought to a normal standard, as you didn’t previously. Learn to say “I was wrong” when you are wrong!

                Edit: could I have said in the first place that I thought that you were wrong? Probably yes and I’ll keep that in mind.