Time for part 3 of my guide for #onsite #selfhosting: register your domain, set up #DNS zone and automatically update dynamic IP via #DynDNS.
This post took me a bit longer to write, because most of the things I'm touching here are new to me.

Again I'm recommending EU-based services and open source software @yunohost .

As always, more than happy to get some feedback!

https://wasi.ovh/yachay/posts/2025/hosting_domain/

Habe heute endlich mein defektes #DynDNS repariert und ein eigenen VPN Server im #homelab eingerichtet.
Voll produktiv.

Als nächstes steht die Einrichtung eines reverse Proxys an.

Mein Ziel ist es eine Möglichkeit für Freunde zu schaffen auf einem #selfhosted #FoundryVTT Server zuspielen.

Und eventuell eine private Cloud einzurichten. Aber immer ein Schritt nach dem Anderen.

This was surprisingly painful, but I managed to make a #NixOS module¹ to periodically update DNS records via the @netcup API. This means you can do #DynDNS with your domain rented via #netcup

Luckily, someone already made a script² to interface with the API. I taught it to determine public IPs and poured it into a NixOS module with proper options.

¹https://gitlab.com/nobodyinperson/nixconfig/-/commit/86991f4f12abbd612ed39d545301eaf49c81d4cc
²https://forum.netcup.de/netcup-anwendungen/ccp-customer-control-panel/p234827-dns-%C3%A4ndern-per-api

Service:

Hin und wieder wird bei DYNDNS eine stabile Host-ID verlangt:

Linux allgemein:
man ip-token
ip token set ::3000 dev eth0
oder im NetworkManager:
https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/nm-settings-nmcli.html

[ipv6]
addr-gen-mode=eui64
method=auto
token=::3333

Damit kommt man ohne DHCPv6 aus und die Hosts müssen nicht ihre MAC-Adresse "verraten".

Wenn jemand die äquivalenten Einstellungen für andere OS oder Tools kennt, kann ja gern damit darauf antworten.

OG crowdfunding: the email and proposal that got #DynDNS launched into a proper datacenter with proper hardware:

https://web.archive.org/web/20010608191341/http://support.dyndns.org/allusers/2-24-2001.shtml

https://web.archive.org/web/20010603133241/http://www.dyndns.org/proposal.shtml

We got $25,000 from strangers (who weren't totally random; they were using a service we provided, after all) on the Internet in just a couple of months. Pretty awesome. And then built it into a real genuine business.

#DynDNS was built on Perl, BIND, Apache, FreeBSD, MySQL, and once we started doing email services, Exim. Our #OpenSource roots went deep, and we had fun with it too.

More #DynDNSHistory time!

One year at OSCON (the O'Reilly Open Source Convention) in San Diego we rented out the hotel bar and brought in a bunch of networked computers for a LAN party. I think this was Quake III era but I could be off by one.

(cont)

So, heute mal auf frischer Wiese angefangen.
Neue #debian VM auf dem #Proxmox läuft.
#DynDNS läuft. #ReverseProxy läuft. #Vaultwarden läuft. Nu aber ab zu Bett...

Today's #DynDNSHistory is answering a question from @drscriptt . #DynDNS accidentally created a quasi-standard with our DNS update "API". To this day, over 25 years later, dynamic DNS updates for many providers go to a URL of "/nic/update" - and that's our fault.

Why this HTTP(S) mechanism instead of "real" UDP/53 DNS updates? RFC 2136 did come out in 1997, but it wasn't well-supported even in BIND (we eventually used it internally and found LOTS of bugs).

1/n

So, #DynDNSHistory seems to be reasonably popular. I can keep picking random topics of interest to me, but also: what do you all want to know? Ask your questions, I will eventually try to answer them. But beware, the answers may be boring! #DynDNS #InternetOldFarts

Since you all liked the server photo so much, today you get a different #DynDNS historical artifact: me!

This is me in the Room Where It Happened, the actual place where DynDNS started - my sister's old bedroom in my childhood home, endpoint of the previously mentioned 26400 bps modem connection.

Exact date unknown, so I can't say for sure if I was working on DynDNS here at the time, but it's of the right era. If you think I look young, you're right, I started DynDNS at 16. #DynDNSHistory

#GoodMorning! #Noip.com is offering a free #DynDNS service. Nice, no problem with that. You have to pay to update the record automatically, no problem with that.

The shit goes wrong when you don't update the record and your domain goes into "redemption" and you cannot remove it or prolong it again unless you pay...

It would be better not to offer a free service than make it a fucking trap to force users to pay. If I've ever cosidered paying - they've lost me.

Who here can educate me on Cloudflare Tunnels?

I understand I can use this both to handle DNS on my dynamic IP and to serve as a firewall to secure the RasPI I’m hoping to run GoToSocial on. But networking and network security are not my forté.

I've had troubles and downtimes of my #selfhosted external services on a daily basis and for quite some time now. Decided to try another #DynDNS provider and switches from #duckdns to #ipv64. Everything looking real good and I haven't had any downtime since yesterday.