[Pdns-users] using both sql + bind backend?

[Mike]

On 4/14/19 9:27 AM, Gert van Dijk wrote:
>
> Yes, on zone transfers to slaves, the file won't be copied as-is, but
> an "interpreted" "autogenerated" version will be sent. That means that
> if you're using the BIND backend on slaves, you won't see the very
> same file contents in terms of ordering, and when using DNSSEC, the
> AXFR will emit the zone signed, adding the RRSIG/DNSKEY records, etc.
>  
>
>     Awesomeness would be able to keep the order of records and comments in
>     sql backend but thats a feature request...
>
>
> The current SQL schema appears to store comments with references to
> zones by ID, not by their zone name. Also, SQL backends store
> information with relation to each other. It does not sound like a good
> idea to me to reference to items not part of the same data source even.
> (Also, what do you mean by order of records? I thought in DNS, records
> don't really have an order, but just for displaying it to the
> user/administrator they may have. But since you're talking about flat
> file BIND zone files, this is under your own control.)

Thanks for your response.

The comments in a zone file, along with the order in which records are
kept, are somewhat important to me and help me be a better dns
administrator by making sure anything I need to know is right where I
need it. This need, for me, exists only on the (hidden) master and
wouldn't need to be propagated to any slaves. I was hoping there was
some kind of interface that would let me use a bind zone file directly
as input. Ideally id love to 'pdnsutil edit-zone <zone>', have it just
like it was in the bind zone file with comments and the order in which
records are kept. I may even like being able to reference another
backend database for 'include' information, so my manual stuff that
needs comments and so forth for documentation, can stay as such, while
the other parts which would benefit from sql backend for automation and
such, could stay in sql. Hmm..


Thanks.


Mike-

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20190415/7d4bb463/attachment.html>