I’ve been running a VPS with the same IP (v4 and v6) for ~15 years, so I’d say its stable enough. What should I use as an upstream source of time in this case that would actually be useful?
You can use pretty much anything except hardcoding pool.ntp.org itself, including individual servers in the pool. You don't have to be a specific stratum or anything, and the monitors are comically generous with time accuracy (+-100ms)
Comments
I wish I could just add my homelab server hostname to the pool, my IP change regularly :(
Would Dynamic DNS be an option?
It needs to be an IP so it can be one of the “A” records returned by dns lookups of pool.ntp.org.
I’ve been running a VPS with the same IP (v4 and v6) for ~15 years, so I’d say its stable enough. What should I use as an upstream source of time in this case that would actually be useful?
You just use a subset of the other known good nodes in the pool as your source. You’re just acting as an edge node for load distribution
You can use pretty much anything except hardcoding pool.ntp.org itself, including individual servers in the pool. You don't have to be a specific stratum or anything, and the monitors are comically generous with time accuracy (+-100ms)
I got a couple of vps'es. Have one without a good cause. How to apply?
I wouldn't be surprised if this was blocked by most ISPs.