Investigate ways to make domain NS refresh faster than 24hrs

[zachsmith1]

Problem:

• In domains controller, we are caching the nameservers and registrar information for the domain in the .status. We allow queueing a manual refresh and also have a 24 hour default refresh that happens. If the user moves their nameservers to datum, it could appear to them that the domain is still pointing to the old DNS host until they manually trigger a refresh or 24 hours has elapsed.

Desired:

• Make domain nameservers more up to date so that within a few minutes its automatically reflected correctly on the domain resource.

Task:

• Investigate a way to keep nameservers more in sync with the state of the world rather than relying on manual force refreshes or the daily refresh.
• Implement the new approach

[drewr]

Response to https://github.com/orgs/datum-cloud/discussions/155 (surprised GitHub doesn't add discussion links...)

[drewr]

I think an initial refresh in the ~hour timeframe would be sufficient. That would give NS propagation a chance. If it's not going to happen in that timeframe then it probably does need closer to a day since 86400s is a common TTL at the domain level. 24 hours for an ongoing check seems sufficient since people rarely change that.

Another option: We time the checks with relevant API calls from the user. Meaning, that if I'm in the portal or API doing "DNS things" I probably care about up-to-date info. Otherwise you just do it when you feel like it.

Either way, since this is informational and not functional, we have a lot of ways to make it more intuitive.