Many options exist, but there should be a way to set the TTL.
A global way to, using the DNS protocol, ideally easily using dig/kdig, to set the TTL for all responses.
An example might be to send a request for 60.set.ttl.dnssrc.fibrecat.org. to set the global TTL to 60, or get.ttl.dnssrc.fibrecat.org. to return TXT "60", to show that setting.
This could be extended later to longer TTL's.
This wouldn't work well on the public instance, where people could be changing the TTL over each other, but should work well on private instances where the user count is lower and/or can be controlled.
Many options exist, but there should be a way to set the TTL.
A global way to, using the DNS protocol, ideally easily using dig/kdig, to set the TTL for all responses.
An example might be to send a request for 60.set.ttl.dnssrc.fibrecat.org. to set the global TTL to 60, or get.ttl.dnssrc.fibrecat.org. to return TXT "60", to show that setting.
This could be extended later to longer TTL's.
This wouldn't work well on the public instance, where people could be changing the TTL over each other, but should work well on private instances where the user count is lower and/or can be controlled.