If your home IP changes and you have to keep fixing the address for your server, I'm building IPKeep to help with that. It gives you a hostname under a.ipkeep.net and keeps its IPv4/IPv6 records updated. I'm the developer and I'm looking for people to try it on a noncritical setup.
Try it here: https://ipkeep.net/
Downloads and setup: https://ipkeep.net/downloads
I'd especially like feedback from Windows 10/11 users, Linux or NAS users who can run Python or Docker, and people with routers that support custom HTTPS DynDNS2 with HTTP Basic authentication. The router endpoint has been tested with ddclient 3.10.0; real router/firmware compatibility still needs testing.
Could you try creating a hostname and setting up one updater, then tell me:
-
Where, if anywhere, did signup or setup become confusing?
-
Did the updater resume checking in after a reboot, and update the record when your public IP changed?
-
If something failed, did the logs and DNS checks help you work out why? Your device, OS/router firmware and error message would help.
IPKeep also has tokens you can restrict to selected hostnames, IP history, DNS comparisons against Cloudflare and Google, and dashboard warnings when an updater stops checking in.
It's free during early testing, with unlimited hostnames. Signup uses Google or Microsoft. DNS hosting is managed by IPKeep; it doesn't update your existing domain's DNS zone or bypass CGNAT. Check-in warnings are in the dashboard, not email alerts. The Windows client is MIT open source, but the current Preview 7 installer is unsigned. Docker is built locally using the guide.
Feedback in the comments is welcome, or use https://ipkeep.net/contact. Please leave out tokens, credentials and Authorization headers. I'd like to hear what worked as well as what got in the way.
Source: r/betatests · by /u/calxibe