2026-10-15 18:53 UTC
Replies (7)
-
@SGG@lemmy.world 2026-10-16 04:34
I use duckdns.org and then make use of CNAME records pointed at the duckdns record for my own domain name/subdomains. My router (unifi device) keeps duck DNS up to date with my changing IP, but there’s lots of ways to get that done. You could consider tailnet or similar as well?
-
@Sliversun@lemmy.world 2026-10-16 05:22
Ddns as others said or use cloudflare dns with cloudflare tunnel
-
@worhui@lemmy.world 2026-10-16 05:43
That is a bit crazy if you are in the US. There is no ‘business Id’ just say you are a sole proprietorship, meaning the business is just you, no corporation structure or anything like that and you are dba, doing business as, and your name. That is how you technically describe yourself when you are a business when you are a person. Your tax id number would just be your social security number. It’s legal to transact business as a person.
-
@solrize@lemmy.ml 2026-10-16 05:43
Proxy through a VPS, or use dynamic DNS if you don’t mind occasionally waiting for TTL expiration when your address suddenly changes. You can set it to 1 minute and that often works these days (it didn’t always). Will your ISP give you a static IPv6 block? It’s v4 that’s scarce, but if it’s just for your own stuff and you aren’t worried about users on old v4 networks, it’s fine to just use pure v6.
-
@stratself@lemdro.id 2026-10-16 06:53
Since nobody mentioned, I recommend desec.io as the DNS provider. Has a good REST API to update records, also provides a dedyn.io dynamic domain, and runs as a nonprofit. I think ddclient will also support it natively in the next release as well. The solution of renting a VPS also works but usually incurs some cost. You might also want to look into Cloudflare Tunnels
-
@Saltarello@lemmy.world 2026-10-17 05:28
Duckdns with cron: invidious.tiekoetter.com/watch?v=z092FGtP6ME Or youtu.be/z092FGtP6ME
-
@miaowoo_lw@lemmy.world 2026-10-18 04:55
The problem you’re describing — reconfiguring things when the IP changes — has a standard fix that costs nothing: a domain with a short-TTL A record updated automatically. Two paths, pick by how your services are consumed: If the audience is you/family: Tailscale or plain WireGuard to a $4-5 VPS, and the IP churn stops mattering entirely — you connect to the VPS/tailnet name, which never changes, and home-IP changes become invisible. This also sidesteps CGNAT if your ISP is doing that. If services must be publicly reachable: dynamic DNS. With a Cloudflare-hosted domain, a cron (curl the API with a scoped token, or ddclient) updating the A record every 5 minutes with a 60-120s TTL means a change propagates within minutes. What you must not do is hand-configure the IP anywhere else — certificate SANs, firewall rules, client configs — everything references the hostname only. Once everything is hostname-based, an IP change is a non-event you’ll never notice. Two honest caveats: if your ISP changes IP while a long-lived connection is up you’ll get one brief blip mid-transfer — nothing reconfiguration can prevent anyway. And if your goal is email delivery from home, a dynamic residential IP is a deliverability problem no DDNS fixes; mail wants to go out via a VPS relay regardless.