feat: Default TTL

[mircea-pavel-anton]

inject a default TTL on all records that don't have one specified via MIKROTIK_DEFAULT_TTL

[mircea-pavel-anton]

As observed during #14

Setting a default TTL also impacts the TXT record generated by external dns to track ownership of records. For some reason (i did not investigate this too much just yet), this prevents those records from being created thus preventing external dns to assume ownership of the created dns records.

Further investigation would be needed for this, but to be fully honest i am not sure if it is really worth the time and the headache to work around this. I would probably just set up something on the k8s side to have a more robust solution that achieves fundamentally the same thing (a mutating webhook maybe?).

[mircea-pavel-anton]

Leaving this here to see if it gains any traction and people would like such a feature added.

[mircea-pavel-anton]

https://github.com/kubernetes-sigs/external-dns/blob/master/provider%2Faws%2Faws.go#L511-L544

This may be relevant? A similar function comparing expected and current state, keeping track of default values.

[nobleess]

hi, I need this feat
my solution #173

[tajinder400]

Interestingly enough, I'm interested in getting this added too. I've noticed when a value of 0 TTL is given to a record, I'm unable to resolve the static DNS names on both Windows and Linux machines. Creating records in the same fashion, or amending them, but adding a value greater than 0 is enough for it to be resolvable by any machine I have.

Do you have this same issue @nobleess ? I'm curious as to your interest in this feature request also?

[nobleess]

I encountered the same issue on Linux machines @tajinder400

[mircea-pavel-anton]

Fixed in #173