• 1 Post
  • 84 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle



  • 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?







  • As long as whatever firewall rules you’re using is capable of resolving FQDNs then I don’t see an advantage of doing this. Maybe in the off chance that your IP changes, someone else gets the old IP and exploits it before the DDNS setup has a chance to update. I think that’s really unlikely.

    Edit: just to add to this, I do think static IPs are preferable to DDNS, just because it’s easier, but they also typically cost money.


  • So here’s my two cents:

    I think that if you have a bunch of services, then you should use caddy or Apache or nginx. doing this in caddy and Apache is not that difficult, but I understand the hesitation (I don’t have much experience with nginx)

    If you just want to get something working you could do bookmarks with the http://host.whatever.com:port and that would be Gucci.

    You could also use another registrar or name server besides Cloudflare to make URL redirect records. This is like an A record but it also includes a port. This is not a standard type of record, but some places will do it like Namecheap.

    Again, if you want to do it the right and best way, then I do think a reverse proxy is the way to go.