I got a homelab, at the moment I am only running some local stuff and tailscale to reach my stuff remotely.

I can use tailscales ddns, but I would like a real domain. Is there a domain registrator that works with dynamic ips? Or do I need to use a CNAME instead of A record?

-2 points

I use cloud flare DNS and it has support for dynamic IPs, my current setup is through a plug-in in my PFSense router

permalink
report
reply
3 points

All domains works with Dynamic IPs - it all depends on what DNS-provider you use :) Provider like Cloudflare ( I do not recommend Cloudflare) and afraid.org both offer dynamic DNS.

permalink
report
reply
3 points

Do you recommend afraid.org?

permalink
report
parent
reply
4 points

Afraid.org is great :) I do recommend

permalink
report
parent
reply
0 points

Yea, that’s right. What I was looking for was like one stop shop. Where I can pay for my domain and dns needs. My current domain registrator does not have dynamic dns, so I have to use a CNAME from another place with a ddns.

permalink
report
parent
reply
1 point
*

Since your name is Hemlig, I assume you are from the Nordics. Loopia has support for dynamic DNS.

permalink
report
parent
reply
4 points

Why don’t you recommend Cloudflare?

permalink
report
parent
reply
1 point

Its market share defeats the point of self-hosting.

permalink
report
parent
reply
2 points

It is a giant MITM proxy, and whoever who has access to their logs have the potential to gain a lot of control

permalink
report
parent
reply
1 point

Don’t have to use their proxy. My gateway router uses cloudflare to set the IP via the API and I just use self-signed certificates. A record resolves to my gateway, not some cloudflare server.

They also do a lot of work in the privacy space. Encrypted Client Hello to protect SNI came from them.

If you use any company for TLS termination they can MITM (e.g. AWS certificate manager).

permalink
report
parent
reply
-3 points

Pro Dynamic DNS service from noip.com will let you have dynamic dns using your own domain names for $20/mo.

permalink
report
reply
3 points

$20/mo?! When free alternatives exist, why would anybody do this?

permalink
report
parent
reply
1 point
*

noip is supported by almost all consumer routers, so you’re probably paying for convenience. For homelabbers with a bit of scripting skill, it’s completely unnecessary though.

permalink
report
parent
reply
1 point

Emphasis on “a bit,” it truly is a simple task to automate. I don’t think that anyone who has need for dynamic DNS should realistically have much trouble tackling that problem.

For anyone who might attempt this and isn’t sure how, here’s what you need. You need a service controlling your domain with API support for updating your DNS records - some have been mentioned here, I just use gandi.net. You need to enable the API for your account/domain. Figure out how to run the command you need against the API from a scripting language of your choice - there should be documentation for the API, and it should be a single API call. Figure out how to determine your server IP from within the same scripting language. Then, write your simple script that determines the right IP and updates the record if it doesn’t match.

All you need to do then is automate running the script - on Linux, a cron job or a systemd service and timer.

permalink
report
parent
reply
1 point

I am unaware of any free services that allow you to use your own domain.

permalink
report
parent
reply
1 point

Does your ISP support IPv6?

permalink
report
reply
0 points

I think I can ask them about it. Never really used ipv6. Maybe that’s even better. Then I can maybe use more than one IP even. I don’t know how the ISPs deal with it. Do I only get one for my router, or can I get a bunch of them… hmm

permalink
report
parent
reply
2 points

with IPv6 you are able to address your internal network devices directly without port forwarding. Just make sure your router and other gear support it so you have everything you need.

permalink
report
parent
reply
3 points

This is the way.

permalink
report
parent
reply
1 point

Yea, my stuff supports it. But I never checked out how the ISPs is dealing with it. I will check it out!

permalink
report
parent
reply
2 points

Silly as it is, many ISPs hand out dynamic IPv6 prefixes that may change once in a while. Or “dynamic” prefixes that never seem to change (but are not guaranteed never to change).

The reason is of course that they like being able to charge extra for static IPv4 addresses, and they see no reason to get rid of that revenue source for IPv6.

permalink
report
parent
reply
7 points

It really depends on the company that you use to manage the domain’s DNS. As long as they have an API to update DNS records…

For example, I can have my domain at Porkbun and have its DNS managed at Cloudflare. Cloudflare allows updating DNS records via API…so there’s programs to update it. Some routers even support it.

Worst case, you can set up a service like duckdns and have your domain, via cname, point to the duck DNS subdomain.

There’s options.

permalink
report
reply
2 points

I think using the cloudflare API is the way to go. You could probably set up an internal service that translates your home router’s dyndns request to a cloudflare API call.

permalink
report
parent
reply
1 point

Only if you had root access to your router. It’s a lot easier to write or find a very simple update script and schedule it to run every now and then via crontab.

permalink
report
parent
reply
1 point

The daemon script is simpler, true. but usually you can just point your router at some dyndns URL and you could put an internal IP for that.

permalink
report
parent
reply
5 points

Porkbun also has an api for updating records.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 4.9K

    Monthly active users

  • 3.9K

    Posts

  • 84K

    Comments