ClickyMcTicker

@ClickyMcTicker@hachyderm.io

• ⁨Comment⁩ on ⁨Lemmy devs are considering making all votes public - have your say⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  @UniversalMonk @SatansMaggotyCumFart I don’t know you, I’ve never seen you before, and I’ll likely never see you again, so feel free to skip reading this, but I’m absolutely not surprised that your posts get downvotes if this is indicative of your average comment. Accusatory, sarcastic, and grating are not the adjectives that I associate with positive energy. I don’t think public voting is going to solve the issue you described.

• ⁨Comment⁩ on ⁨Setup a DNS server on a dynamic public ip⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  @papelitofeliz
  3. Set up your PiHole on a static private IP.

  4. Ensure both sites can route across the tunnel. Based on your experience level and scope, dynamic routing is not recommended or necessary, which means static routes. Point a route for each side’s subnet to the Wireguard tunnel IPs so your firewalls know how to reach and respond to each other across the tunnel.

  5. Configure your devices to use PiHole for their DNS, via DHCP ideally.

• ⁨Comment⁩ on ⁨Setup a DNS server on a dynamic public ip⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  @papelitofeliz
  VPN for sure:

  1. Set up both locations with Dynamic DNS providers. DuckDNS is free, but if you’re building infrastructure you may as well buy your own domain and set it up through that (Namecheap is what I use and recommend).

  2. Set up a Wireguard tunnel between both locations. Do *not* specify an endpoint for either. You could specify endpoints to boost security (barely), but it will cause your system to fail during IP changes, for the duration of the TTL.