User Specific Configuration Limits/Restrictions

Not sure the “user specific” part of it is right, however I’ll explain so maybe it’s clear

So this was a thought out of me doing some work with our DNS zones around TTLs. It had really become the wild west, and there was a large range of TTLs (5 secs to 24 hours).

I was wondering if a new feature might be a configuration section where you can specify things like:

• Minimum TTL
• Maximum TTL
• Valid Regions (GeoDNS)
• Etc.

This might tie into #75, where we specify extra configurations like default TTL.

I’m mostly thinking about the TTL use case. If I try to run noop or doit, it will error saying it is less than or greater than Min/Max TTL, and if I dump it will error during the dump, and if you say lenient it will dump it with the current value, but again, you hit the error applying.

Wondering if there is a place for something like that.

---
config:
  default_ttl: 3600
  min_ttl: 300
  max_ttl: 86400

providers:
  config:
    class: octodns.provider.yaml.YamlProvider
    directory: ./config

[ross]

and I believe a list of acceptable ones, eg [300,3600,86400]

That’s easy enough to add to https://github.com/octodns/octodns/pull/933

[yzguy]

@ross I actually haven’t done anything with OctoDNS + Geo 😛 so I don’t have any strong opinions about if it’s necessary. The specific use-case I had for this was just setting a minimum, a maximum, and I believe a list of acceptable ones, eg [300,3600,86400]