Why use this plugin instead of the built in file plugin?

Is it just the "inline" aspect of the configuration? Or are there other features (like the optional SOA?)

If _file_ supported inline configuration, could we deprecate _records_?

Start by comparing the records plugin with CoreDNS's built-in file plugin, focusing on inline configuration and the optional SOA feature mentioned in the issue. Done means reaching and documenting a clear decision about whether file should gain inline support and whether records could then be deprecated.

Written by the indexing model from the issue text.