sabreW4K3@lazysoci.al to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.comEnglish · 2 days agoGoogle Receives Piracy Shield Orders to Block Pirate Sites in Public DNS * TorrentFreaktorrentfreak.comexternal-linkmessage-square23fedilinkarrow-up190arrow-down10
arrow-up190arrow-down1external-linkGoogle Receives Piracy Shield Orders to Block Pirate Sites in Public DNS * TorrentFreaktorrentfreak.comsabreW4K3@lazysoci.al to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.comEnglish · 2 days agomessage-square23fedilink
minus-squarequediuspayu@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up2·edit-22 days agoDo I need a static ip if I plan to only use it locally from my home network?
minus-squarereluctant_squidd@lemmy.calinkfedilinkEnglisharrow-up4·1 day agoWhat I suggest/have done: Rent a cheap VPS in a non-five eyes country that comes with a static ipv4. SSH on random port with certificate auth only. No root, no password auth. setup WireGuard server with random port. firewall block all incoming except ssh and WireGuard port at first. set home server to connect via wireguard as sole client to VPS. individually add any ports you want to go to the home server from the internet as NAT forwarded ports. Basically WWW -> VPS -> Home. have a separate WireGuard VPN for outgoing from the home server. profit? But it’s crazy complicated. At least it was for me. Not for the faint hearted imo.
minus-squaretkw8@lemm.eelinkfedilinkEnglisharrow-up9·2 days agoThe box on which the dns server runs will need a static internal IP address.
minus-squareNawor3565@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up7arrow-down1·2 days agoIf you’re only going to use it from within your own LAN, then no, you don’t need a static public address
Do I need a static ip if I plan to only use it locally from my home network?
What I suggest/have done:
Rent a cheap VPS in a non-five eyes country that comes with a static ipv4.
SSH on random port with certificate auth only. No root, no password auth.
setup WireGuard server with random port.
firewall block all incoming except ssh and WireGuard port at first.
set home server to connect via wireguard as sole client to VPS.
individually add any ports you want to go to the home server from the internet as NAT forwarded ports. Basically WWW -> VPS -> Home.
have a separate WireGuard VPN for outgoing from the home server.
profit?
But it’s crazy complicated. At least it was for me. Not for the faint hearted imo.
The box on which the dns server runs will need a static internal IP address.
If you’re only going to use it from within your own LAN, then no, you don’t need a static public address