provide a hostTTL function

[kloenk]

Currently its a little annoying to create a subdomain host with a specific TTL. I would suggest something like the following:

{
  hostTTL = ttl: ipv4: ipv6:
     lib.optionalAttrs (ipv4 != null) { A = [{ address = ipv4; inherit ttl; }]; } //
     lib.optionalAttrs (ipv6 != null) { AAAA = [{ address = ipv6; inherit ttl; }]; };
}

[kirelagin]

I think you can do either:

{
  subdomains.foo.A = [ (a "1.1.1.1" // { ttl = 50; }) ];
}

or

{
  subdomains.foo.A = [ (ttl 60 (a "1.1.1.1")) ];
}

I think it would also help if the ttl combinator could work recursively so that you could apply it to an entire zone/subzone.

Regarding creating simple subdomain hosts, I completely agree that it’s annoying, however I don’t know how to make it better in an unambiguous way. I was thinking about building yet another higher-level DSL on top of this one, that would be ambiguous but would allow for easier hosts definitions.

[kloenk]

Your ttl function would mean, I would have to specify A and AAAA records separately. My idea was to create a shorthand function for this.

[eyJhb]

Is there anything that goes against specifying a default TTL, and then editing it on a case on case basis?

EDIT: I stand corrected, there is a $TTL. Sorry! But for subdomains it would be nice as well :)