Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I have a cronjob that runs every minute to update the IP address. I could try to increase it to every hour or so. In the beginning I tracked how often the ISP changed the address and it was roughly like once every 24-30 hours, cannot really remember.
Agree with the other 2 replies that hammering the dyndns server every minute is excessive and you should only send them updates when your IP address actually changes.
You should also check the TTL on the primary name server (the dyndns server) and the DNS server you use (likely your ISP's DNS server).
https://johncireland.wordpress.com/2020/09/07/viewing-dns-record-ttl-on-windows/
The dyndns server probably has it configured right and it should have a low TTL like 5 minutes or below, but sometimes the DNS server you use can be a server that ignores TTL and caches the result for longer than expected. I don't think this is the problem if multiple of your friends are having the same problem but it doesn't hurt to check.
Maybe change the script to just send updates whenever the ip really changed.
That does seem excessive. Change it so that it only sends an update to dyndns when it actually changes.
Having a new ip every 30 hours also seems pretty aggressive. I guess the DNS change might be slow to populate servers in that time if it is a "weird" top level domain.