Vultr DNS default TTL

[d19dotca]

I noticed Cloudron uses a TTL of 300 seconds when using Vultr DNS.

Knowing it uses a lower TTL of just 30 seconds when using DigitalOcean DNS... If the desire is to have the lowest TTL possible, then I'd suggest Cloudron change the default TTL when using Vultr DNS to 120 seconds instead of 300 seconds since Vultr seems to support a lower TTL of just 120 seconds.

https://www.vultr.com/docs/introduction-to-vultr-dns/#Limitations

[girish]

@d19dotca ah nice, 300 used to be the lowest before. Looks like it's changed now. Will push a fix.

[d19dotca]

@girish Any ETA on when the next version of Cloudron would ship which includes this change? Also (and more importantly), would it override the existing TTLs for items managed by Cloudron to be lower or will it leave the existing TTLs as-is? Wondering if there'd need to be a bit of a cleanup afterwards to set the lower TTLs manually if needed or not.

[girish]

@d19dotca The change is in 7.2.1 which we will release next week.

Having the TTL value is not that important. We keep it low only for the use case of a user wanting to re-use the domain for some other purpose. For example, let's say you install app.domain.com. Then, decide to use that domain for something else outside cloudron. If that domain had a very high TTL, then it's going to take a long time to clear out the DNS caches. By keeping it low, we (cloudron code) are just being friendly.

[d19dotca]

@girish Thanks for the update.

I'm familiar with TTL and why it's kept low, but I guess I'm just asking if it'll "correct" the TTL to the lower value after upgrade or if it'll keep them as-is and only newer ones will use the lower TTL.

Reason for the ask is because I tend to use double the TTL value used by Cloudron in order to distinguish my own custom DNS entries from Cloudron-managed DNS entries. So 'OCD Dustin' will want to make sure things are cleaned up nicely.

[nebulon]

@d19dotca the code will not update the TTL automatically for existing records, since it only checks if the record value (for A records the IP) is different and only then update.

[d19dotca]

@nebulon I'm just thinking about this some more... would it perhaps make sense to have it not touch the TTL by default if a record already exists, but to force the TTL to be in-sync with Cloudron's preferred TTL if one was to invoke the Sync DNS option manually? I think that'd be a good balance and would help people keep their TTLs optimal / matching Cloudron's intentional TTL value used.

[d19dotca]

Also quick question: What version of Cloudron contains the lower TTL? I see 7.2.1 is listed in the changelog but neither 7.2.0 or 7.2.1 contain anything about the Vultr TTL change, but it seems committed at https://git.cloudron.io/cloudron/box/-/commit/935da3ed153caf5e301a2a0b754c11d4d379a850

Any ETA on when it'll be out?

[nebulon]

@d19dotca we don't know yet when 7.2.1 will be out. If you need the change immediately, you could just adjust the value directly in the code and restart the box daemon. Usually patching the code like this is not recommended, but in this case the change is rather small and will not cause any issues on update later.

[d19dotca]

@nebulon Totally fair, thanks.

Any thought to my earlier suggestion before I asked about the version update? Was suggesting that perhaps TTL can be left alone as you’ve designed it currently; but that it can be updated to Cloudron’s preferred TTL during a manual DNS sync initiation by an admin. Would love to see that be possible.