>>Main Idea: TTL override is useful in tons of situations, particularly where DNS is changing often and you get tired of constantly flushing the client DNS cache as you make changes. Overriding in the client or in the server is overbroad, has poor controls, and thus has consequences far beyond the intended target and must almost always be undone and tracked, making it seldom worthwhile.

>> Request: The killer middle-ground is selective TTL override by domain/regexp, which is a natural addition to Mikrotik's FWD record type. With it, you could just cut down (lower TTL) or outright cull (TTL=0 or =1) DNS caching, but just for domains where you want those clients to always check the server for any changes/updates (very useful in private Dynamic DNS situations, like Windows AD/DNS, but useful far beyond that too). Of course, you could also force the cache to be much higher too in situations where it is needed. I'm assuming the Static DNS entries are processed in order, meaning you could work out your own exceptions or other issues by putting narrower regexp rules above the broader domain rules if, say, you wanted specific entries to stay high.

>> Interface: Can just reuse the normal TTL box/time-parser from A entries and add it to the FWD record type, so no new code needed there.

>> Stretch/2nd Request: It would also be cool to also have a RECORD TYPE field in FWD rules (or make them accessible/controllable via the regexp), as that would maximize the feature and give all the control one could ever want for any FWD situation (independent of my TTL suggestion above).