If your using cloud flare you can write a script to use there API and update your domain name for you.
Set the script to run on internet failure since most ISPs won't change DHCP lease while live.
this post was submitted on 19 Nov 2023
4 points (83.3% liked)
Home Networking
189 readers
1 users here now
A community to help people learn, install, set up or troubleshoot their home network equipment and solutions.
Rules
- Please stay on topic.
- Please use the search function to look for keywords related to what you want to ask before posting since most common issues have been answered.
- No Ads. This community is for support and discussion. Ads and self promotion are not welcome here.
- No product reviews or announcements. If you have a question about a product, be specific about what you want to know.
- Be civil. Don't be a jerk. Not being a jerk is surprisingly easy.
- No URL shorteners. URL shorteners tend to hide the real use of a link. For this reason, please use normal links, even if they're long.
- No affiliate links.
- No gatekeeping. With profession shall come professionalism. Extend help without judging others for their ignorance. The same goes for downvoting of comments or posts for "stupid questions" or not being as knowledgeable as others.
founded 10 months ago
MODERATORS
Some DynDNS plugins, like OPNsense, support CF built-in. Very useful.
Don't know. But afraid.org works good for me..
If you use Cloudflare als your dns (you can transfer your existing domain) you can setup a cronjob that basically functions as a dynamic DNS. Then you only need to run this cronjob inside your home network. It's free if you already have a domain and something that runs 24/7 inside your home network
Could be that there are quite a few domain-providers that does not have an API to easily change the config directly at their service.
Personally I use a script and cron to check if the public IP have changed, and if it has changed, it updates my settings at the domain-provider with just a curl-command.
$9.0/ month for dynamic dns.
That is the pro version that is up to 50 different hosts, etc.
The "home" user version that you don't have to validate every 30 days is 1.99 a month.. And they still have a free version as well. You just need to confirm it every 30 days.
True but my understanding with the $1.99/month l can't use my own domain.
Ive been using no-ip.com DDNS for over a decade with my domains. The DDNS client is in my OpenWRT router. It configures 'myhost.no-ip.com'. In the DNS config for my domain, I just setup CNAME entries for the hostnames I want on my domain, and point them all at myhost.no-ip.com. It works perfect. I pay $25/year for no-ip.com.
If you own your own domain, no-ip wouldn't be where I would go no..
I doubt that 9/month price is intended for "home" users.. 50 hosts, this seems more suited for a smb that doesn't really have some senior network engineer setting everything up for them.. And more the guy got promoted to IT because hey he knew how to setup the wifi router ;)
For some smb, with a few locations and wanting to have some fqdn point to their changing IP because since well they only have consumer level connections, etc. And they don't understand how any of it works anyway.. 100$ year seems a fairly reasonable price.
Why pay anything when DuckDNS is free?
I believe they're just greedy
Any used Dynu.com They seem dead cheap but full indepth domain management is lacking. Unless l'm missing something.
I can ask the same about wildcard DNS. Even if you are willing to setup a docker container to keep your DNS updated no matter where it is hosted, normally you can only do so with one domain at a time. Want wildcard redirects? Most providers make you switch over to a virtual dedicated hosting. Thankfully cloudflare exists. You have full control over DNS, it’s free and they allow you to set www subdomain to a nameserver of your hosting provider and use dns trickery to cname the root domain to www, leaving all of the other subdomains free for you to use as you please.
Ok will check for more infor.
Setting your www directly to an A / AAAA record is easier, but using NS records instead allow your IP to change as your host changes it as if DNS was setup directly with the hosting provider. Learned my lesson last time my host decided to change the IP my service was hosted on.
You can than have a subdomain like home. where you maintain your public IP and a wildcard *. CNAME redirect to home. so that you can use nginx to expose your services easier, such as homeassistant., nodered., plex., etc...
Many domain registrars don’t have an API, so then services like no-ip are your only option.
They charge this because people pay it. Maximise your ROI as far as you can get away with is a staple of many industries.