Hello,
I would like to include .bit domain in my own DNS. I prefer not to delegate the requests to a third party DNS and serve them from the blockchain. How do you setup your own DNS server? Is there a tool that convert d/ names to bind zonefile?
Thank you,
J.
Namecoin to zone file
Forum rules
Warning !
Avoid using binary softwares from untrusted users.
Prefer compiling it yourself and verify sources.
Warning !
Avoid using binary softwares from untrusted users.
Prefer compiling it yourself and verify sources.
Re: Namecoin to zone file
On https://github.com/sysfrog/namecoin there's a script that generates a maradns configuration. Shouldn't be too hard to adapt this to bind.
-
itsnotlupus
- Posts: 12
- Joined: Mon Jul 04, 2011 12:55 am
Re: Namecoin to zone file
I've written a little node.js script that will generate various conf. files from the namecoin blockchain.
https://github.com/itsnotlupus/nc.dns.gen
It's likely to be a bit buggy, but it should get you closer to what you want.
https://github.com/itsnotlupus/nc.dns.gen
It's likely to be a bit buggy, but it should get you closer to what you want.
Re: Namecoin to zone file
Thanks to both of you, I will play with them.
Re: Namecoin to zone file
https://github.com/sysfrog/namecoin link is broken
So is http://bluishcoder.bit/bitcoin-pool/namecoin-hosts.c (hosts.txt)
Do anybody have a backup copies?
UPD Oops, I've noticed the "bit" part in "bluishcoder.bit".
Due to lack of viable options, I'm still not .bit*enabled.
So is http://bluishcoder.bit/bitcoin-pool/namecoin-hosts.c (hosts.txt)
Do anybody have a backup copies?
UPD Oops, I've noticed the "bit" part in "bluishcoder.bit".
Due to lack of viable options, I'm still not .bit*enabled.
Re: Namecoin to zone file
Try: http://www.bluishcoder.co.nz/bitcoin-po ... in-hosts.cOCTAGRAM wrote: So is http://bluishcoder.bit/bitcoin-pool/namecoin-hosts.c (hosts.txt)
Do anybody have a backup copies?
Re: Namecoin to zone file
Is there a DNS server available that is only capable of zone transfers? This way we could configure the DNS we already use (I'll never use BIND, for instance, thanks to DJB's advertisement) in an universal way. NameCoin AXFR should be configured by, probably, the only argument: suffix. For instance, "rewrite.toom.su" will make gee.bit projected into gee.bit.rewrite.toom.su.
UPD Sorry to mislead you, it is not possible to keep up to date DNS via AXFRs inside some suffix. Using AXFRs it is only possible to keep up to date .bit zone with delegations (SOAs), As, AAAAs, MXs and other records WITHOUT any suffix.
DNS suffix server must perform resolving on its own and serve answers like an authoritative server. If we, for instance, send answer that gee.bit.rewrite.toom.su is delegated to gee.bit's DNS, an ISP-side recursive DNS will query gee.bit's DNS for gee.bit.rewrite.toom.su. gee.bit's DNS doesn't serve this domain and won't resolve this query. So in the end of the ends, DNS suffix server must perform resolutions on its own completely.
UPD Sorry to mislead you, it is not possible to keep up to date DNS via AXFRs inside some suffix. Using AXFRs it is only possible to keep up to date .bit zone with delegations (SOAs), As, AAAAs, MXs and other records WITHOUT any suffix.
DNS suffix server must perform resolving on its own and serve answers like an authoritative server. If we, for instance, send answer that gee.bit.rewrite.toom.su is delegated to gee.bit's DNS, an ISP-side recursive DNS will query gee.bit's DNS for gee.bit.rewrite.toom.su. gee.bit's DNS doesn't serve this domain and won't resolve this query. So in the end of the ends, DNS suffix server must perform resolutions on its own completely.