@tynes Thoughts about making this a plugin vs an RPC call? Perhaps both will work well, but I was thinking a plugin might give us more flexibility with configuration e.g. file format, write to disk every x minutes.

I think that the base functionality should be a RPC. Then everybody has the functionality built into the daemon without needing to install another package for the plugin. I think that a plugin could be useful for extending the base functionality, in particular the write to disk every so often job. You can also get this functionality with a cron job or an event that hs-client listens to. I think the proper solution would depend on the particular security constraints. Getting feedback from people who run large scale DNS infrastructure or people that have a particular use case for this RPC would be helpful for helping us decide exactly how it should work.

My usecase involves dumping the state of the Handshake zone in JSON with extra details so that it is possible to make visualizations of the tree. I'd personally like to listen to an event using hs-client, maybe something like tree update, so that I can call dumpzone filename /*json=*/true /*detail=*/true right after the tree is updated

Bitcoin has a similar RPC method called dumpwallet
https://bitcoincore.org/en/doc/0.16.0/rpc/wallet/dumpwallet/

Ah yes good point, I think plugin to extend base functionality would be best as well.

Happy to help work on this if it's needed!

@tynes, we have a full implementation of the zone file format in bns:

• https://github.com/chjj/bns/blob/master/lib/internal/scan.js
• https://github.com/chjj/bns/blob/master/lib/internal/schema.js

As far as dumping to zone file goes, I have some code written for this currently (along with the new record types). Will push soon.

@chjj Encoding a name's wire data to a Zone file would make public resolvers like hs.zone a lot more reliable. Any update on that?

As far as dumping to zone file goes, I have some code written for this currently (along with the new record types). Will push soon.

@chjj was this merged?