ThreeHalflings

@ThreeHalflings@lemmy.world

• ⁨Comment⁩ on ⁨Trying to revive r/aaaaaaacccccccce here on fediverse. Come visit us if you are Asexual and/or aromantic, or just love our memes and humor.⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Wiat, you don’t believe in sexual preferences? People aren’t allowed to decide what they will or won’t stick their dick into now?

• ⁨Comment⁩ on ⁨Etymology – For fans of word and phrase origins to learn and share interesting findings⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Love it. I’d never have thought to look for it, but I’m glad I stumbled across this post!

• ⁨Comment⁩ on ⁨Ideas wanted⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  OK, I didn’t read before answering, probably ignore my answer below but I’ll leave it up incase someone learns something from it.

• ⁨Comment⁩ on ⁨Ideas wanted⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Sounds like what you are tyring to do is called Split Horizon DNS.

  Requests from outside your network should revolver server.domain.com to the public IP, but requests from inside your network should resolve it to the private IP.

  If that’s what it is then you register the public IP with your nameservers. You also run a DNS service internally which you point all your computers at (likely by putting it as the DNS server in your networks DHCP settings). That DNS server is set up to return the private ip addresses for all your servers, and to forward any other requests to some external DNS like 1.1.1.1