Comment on Own domain for Jellyfin and privacy concerns
dingleberrylover@lemmy.world 3 weeks agoThanks, yes I also use a script that constantly sends the current IP address to the dynDNS provider. I could be completely wrong, but the internet connection of my friends house where the server stands is fine even during these connection issues. So I would blame the DNS resolution, but it is also my first time running a server.
lorentz@feddit.it 3 weeks ago
How frequently do you send these updates? Most of dynDNS provider rate limit the updates you can send, so it is possible that you send a bunch of useless updates when the IP didn’t change and the actual update that is required gets discarded because you hit the limit.
Do you log your script errors somewhere? Are you sure that the IP changes so frequently?
I know at least 3 European fiber providers which offers static IPs. For broadband always on connections IP changes should be pretty rare
dingleberrylover@lemmy.world 3 weeks ago
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.
amphetaminisiert@feddit.nl 3 weeks ago
Maybe change the script to just send updates whenever the ip really changed.
teslasaur@lemmy.world 2 weeks ago
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.
1Fuji2Taka3Nasubi@piefed.zip 2 weeks ago
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.