biolizard89 wrote:Personally I prefer ncdns:
https://github.com/hlandau/ncdns
It follows standards much more closely than NMControl and (I think) DNSChain. At the moment, ease of install is somewhat worse than NMControl, which is why it's not yet available at
https://namecoin.org (and also probably makes it less suitable than NMControl for you, given that you appear to prefer automated setup).
I'm unaware of any bugs in ncdns that might impact IPv6 -- IPv6 support is in the code, so if it doesn't work, it's a bug.
Thanks Jeremy,
I am adding both ncdns and DNSChain to my project as .bit DNS resolver.
I tested ncdns and it resolves IPv4 and IPv6 .bit domains with legacy specs as well.
DNSChain resolves IPv4, but with new specs. I added IPv6 resolving code in my own repo and will be using that repo to include in my project.
Will be putting option in my project giving users option to choose their .bit DNS resolver through Web UI. With either of the .bit DNS resolver service they should be able to access .bit websites setup with IPv4 and IPv6. I needed IPv6 support mainly because I'm including cjcns as feature to my project, and cjdns only works with IPv6.
ncdns will be the default .bit DNS resolver service, as it uses less RAM than DNSChain when the service starts, and it has the required feature which project needs.
This is what I'm working on:
https://github.com/satindergrewal/Super ... lpha-0.0.3