RFC: optional zone_name parameter for DNS service drivers #214
Description
It's come up once or twice in discussion: a suggestion that some drivers might be much simplified if the user could just TELL them what zone (usually means what domain.tld, very like a bind9 zone) the records are to be added to/removed from. Several providers have to grovel through possibly paged lists of info to search for the relevant zone, while in many cases the user knows very well which zone applies.
Of course this wouldn't be a 100% generic approach. A single user looking to create a shared certificate for hosts that are in various of his multiple service-side zones wouldn't be able to specify one single zone (unless maybe he setup aliasing to that one special zone...). And it would require migrating the driver to the new interface [not going to add more parameters to the legacy interface] in order to have access to the zone_name parameter. Nor could I see breaking existing behavior of those legacy drivers that currently have to grovel - that would have to remain as the fallback. Perhaps a new version that requires the zone_name because it omits the grovelling? Maybe. Have to be given a different name, though.