@txt_file if #mosh can do tunneling over #TCP then you essentially have #SSH-#Tunneling over #Tor...
I'd say that is a valid use-case espechally since @torproject #OnionServices are way better than #DynamicDNS and/or #PortForwarding techniques as they also anonymize both source and destination.
#blog
ZeroTier – domowy VPN bez publicznego adresu IP
https://blog.tomaszdunia.pl/zerotier/
#Android #DHCP #DuckDNS #DynamicDNS #HomeAssistant #iOS #IoT #NabuCasa #NoIP #OpenVPN #SelfHosted #VPN #Wireguard #ZeroTier
Reminder for casual #DNS admins (like me) who are #SelfHosting : instead of sticking (or fighting) with your registrar's own #DynamicDNS service you can just choose any dynamic DNS service that fits your needs and use the generated domain name as a CNAME entry for the target domain in the zone file at your registrar...
Huch, was für ein äußerst netter Dynamic-DNS-Dienst: https://dynv6.com - sogar mit Delegate von eigener (Sub-)Domain. Und auch noch kostenlos.
Moving my dynamic DNS for my home broadband to @beasts account as it had stopped working on Dreamhost. After starting to write a python script like I was using before, I realised that a simple .netrc file with API credentials and one curl command in a crontab was all I actually needed! Simples! #ddns #dns #dynamicdns
Nerdy #Homelab owners, what is your preferred #DynamicDNS solution and why? #SelfHosted #SelfHostedSoftware
New Episode: hpr4203 :: Setup DuckDNS on a Raspberry Pi
Hosted by Kevie on 2024-09-11 is flagged as Clean and is released under a CC-BY-SA license.
Tags: #DynamicDNS, #RaspberryPi, #RemoteAccess, #Linux.
when I want to expose an app running on my home-network:
when you are self-hosting at home, and you want to give friends access to your jellyfin, whats your preferred way of doing this? My focus is on security, but I'm not an expert on this.
Right now, what I have done is, I set up pivpn with a firewall that exposes only the jellyfin ip/port, so that other stuff on my network isn't available to connected users.
However, their whole internet traffic would go through my network now (if not split-tunneled), unless I restrict internet access, which would also be a dick move of me to people who forget to switch off the VPN 
I was now thinking about setting up a reverse proxy, instead of this whole VPN idea.
How is the security when I'm using a dynamic DNS, that points to my home-network, where I'm using a reverse proxy to catch the requests and expose only jellyfin? How is the security level of a reverse proxy vs vpn?
Looking forward to reading opinions and ideas!
Ok so #DynamicDNS on the very cheap, explain to me please. I can bash and such.
At the moment I'm paying DigitalOcean for a public IP address, and I now have PublicIP at home.
PublicIP at home: not sure if stable, too soon to tell, so best get the infrastructure in place, and then I can shed that monthly bill.
I'm also hosting a couple of unimportant things on it but I have been told by my new fibre isp that it's fine for me to host my private-use servers at my own address, so that's nice.
Cancelled my ancient Dyn account, which was up for renewal on the eighth. I'm a little sad that I had to give up this-server.kicks-ass.org, but the move to a self-owned domain is probably better in the long run.
Looks like I've just lost my #NoIP #DynamicDNS hostname that I've been confirming every month for a good 7 years (despite the server I used it for being down for the last 6), in the hope I'd be able to spin up my Gopher server again: it's just gone into redemption mode so I'd have to pay to get it back...
#RIP qselfgnk.ddns.net.
Does anyone experienced with #SelfHosting and #DynamicDNS #DDNS have opinions about TTLs for home servers?
I'm working on setting up an old laptop for hosting my projects and personal site, but I'm also paranoid about leaving my home network open to the internet.
I currently use Cloudflare, but I'm unsure if the default TTL for proxied records (five minutes) is sensible for DDNS.
DynDNS is now paid only, so set up NoIP for free in about 5mins instead. Screen sharing on Mac, RealVNC viewer on the other machine(s) and NoIP app updating my home IP to the service every 10mins 
#dynamicDNS #remoteAccess #vnc
I haven't been very happy with any of the #dynamicdns update scripts out there for #DigitalOcean, so I made my own in #Python. Has some decent error checking and a separate config file, plus I worked in #IPv6 updates as an option if that's your jam. #homelab https://github.com/elforesto/digitalocean-dyndns
@jwildeboer @EU_Commission that being said, #DTAG are shit as #ISP and forcibly disconnecting & reallocating IP adresses is the norm on ALL consumer tariffs with no SLAs whatsoever.
There's #DynamicDNS, #MultipathTCP and #VPN as well as @torproject #OnionService|s for that scenario!
https://social.wildeboer.net/@jwildeboer/110247910485847487
I specofically have an Enterprise Tariff to avoid these pitfalls...
@valhalla
Credo sia una pistola ad acqua. Un qualsiasi #dynamicdns abbinato a #theonionrouter e gli bagnano il naso.
Per non parlare poi di #i2p.
Chi ha le competenze gira attorno a questi provvedimenti ridendoci sopra.
Ecco forse sarebbero efficaci contro gli #utonti
@informapirata @AlbertoeFabio @ThinkingRaven
Does anyone have experience setting up a #mastodon instance on a #RaspberryPi on a home network and using #dynamicdns to connect to it?
I am not sure if that kind of setup is supported?
I get through the entire install just fine but nginx won't start after I successfully add certs with letsencrypt.
Do I need to #PortFoward any specific ports other than 80 and/or 443? I feel like I am SO close!
I've configured my #dynamicDNS to use Cloudflare and now I want to setup a Cloudflare Tunnel to work with #yunohost.
This bit confuses me.
1. These docs: https://yunohost.org/en/dns_config say that I need to add these details to my DNS
But if I am using Tunnel, do I still need to configure these DNS records?
2. If #yunohost is being installed on sub.mydomain.org, do I create a CF Tunnel "network" or "application"?
