You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
First: I know that modifying records is considered dangerous or technically inappropriate in most circumstances. However, there are conditions where certain modifications might be "less bad" than the alternatives. For example: operating recursive resolvers with single-homed connectivity across very latent (satellite, or even analog) bandwidth creates conditions where TTL shortness causes excessive delays for clients. Having the ability to both examine and modify TTLs on records would be useful in these topologically-distant locations to prevent significant client-observable delay on replies. The potential failure penalty for longer TTLs may in these conditions be an acceptable risk, and is left to the local administrator to manage.
It may be the case that a more suitable implementation is to create a suite of methods that allow for modifying any component of the entire RR answer. The larger scope of other possible methods for RR editing is left open to the kind soul who ends up developing code for this request, but the specific limited hope here is for TTL re-write.
The text was updated successfully, but these errors were encountered: