[gregKeymaster]

Oops, sorry, the days are blending together. Will look into this tomorrow (Tuesday). Hope to merge it same day as well, but if not then sometime this week.

[gregKeymaster]

Awesome, great stuff Satinder! 🙂

I'll get to this ASAP (tomorrow am teaching, but should have time after that).

[gregKeymaster]

Can you send a pull request? It will make it easier for me to see what the differences are and review them.

[gregKeymaster]

The low-level DNS stuff is handled by the native-dns (AKA node-dns) module. That module actually relies on another module called native-dns-packet.

So, does that mean the IPv6 stuff is available in these libraries, but only part that needs to be done is in DNSChain? Or these two also might need some update?

I honestly don't know whether they need updating or not. They do support the AAAA record I believe, so give it a try.

[gregKeymaster]

Hi,

I'm working on a project which will include DNSChain, and will be a major part of it. More info here: https://nxtforum.org/general-discussion/all-in-one-nxt-supernet-freemarket-meshnet-raspberry-pi-device/

Wow, that looks very cool! 🙂

My Github address: https://github.com/satindergrewal

I want to know if there's any progress towards IPv6 support in DNSChain. I'm still new to CoffeeScript, but trying to understand it as much to my ability. Where do I look for the code which handles A record queries. It must be the similar code to implement AAAA, with the conditions to check if the IP is IPv6 or not. Could there be any other complications in implementing IPv6 in DNSChain? Has it been tried to implement before in DNSChain? If so, what were the issues?

We haven't tried implementing IPv6 in DNSChain.

As far as where to look, there are a few places I would recommend:

• src/lib/blockchain.coffee — this is the template that's used when adding support for a new datastore (like NXT, Namecoin, etc.). Search for a comment with “IPv6” in there.
• src/lib/dns.coffee — although no IPv6 comments here, it's a very important file as it's the high level file responsible for most DNS stuff (the other being the dnsHandler key in blockchain.coffee.

The low-level DNS stuff is handled by the native-dns (AKA node-dns) module. That module actually relies on another module called native-dns-packet.

Hope that helps! Let us know if you have any other questions.

[gregKeymaster]

Well, what happens if you set your DNS IP to our website's IP? Does it work then?

And what do your DNSChain logs say? (Make sure to set the log level to debug in your dnschain.conf.)

[gregKeymaster]

Does loading http://okturtles.bit work?

[gregKeymaster]

Very cool!

Have you had a look at BlockchainID? Could be very useful for what you're doing.

Also keep an eye on the dev branch of DNSChain. We've got a huge release we're working on and lots of new stuff (and important refactoring) has been done.

[gregKeymaster]

Unfortunately that didnt seem to work.  I Uninstalled and re-installed coffee and dnschain and used the new conf file.  The error is still there but is not exactly the same as you show.  I have pasted the entire redundant list of errors below… all of it 🙂

I tried removing the dnschain.conf file completely, and the error is the same.  It feels like dnschain is not reading the dnschain.conf file.  Not sure iif it is supposed to create one if it is missing, but none nothing seems to be created.

As a cross check, i tried installing dnschain on another device (a Cubieboard running debian) and it seemed to install and run without errors.  I dont have namecoin on that device, but i may try adding it and use that as my platform for now.  In any case, the problem seems related to my Linux Mint 17 64 bit 386 environment…

Thanks for the help.  It looks like it will be a really useful tool for using namecoin once I get it up and running!

OK, I think you're right in that it looks like it's simply not reading the config file.

You have specified NO_OLD_DNS but it's complaining about NATIVE_DNS.

That doesn't make sense though, because it shouldn't give you an error for that since that's the default and it's a perfectly acceptable value.

My guess is that there might be multiple issues going on.

Check:

• That the DNSChain process can read /etc/dnschain/dnschain.conf
• That changing oldDNSMethod in the config results, at least, in a different error message

And that you don't have some silly typo somewhere.

[gregKeymaster]

OK, I was able to reproduce the error, but it seems that you didn't copy the complete error, which should be:

Code:

error: [Global] No such oldDNS method: NO_OLD_DNS # no quotes around this either

Apparently it does not ignore the comment (which begins with the # symbol). I've just pushed a fix to the README to move the comment to the line above. That should be all that's necessary to fix it (move the comment to the line above).

Sorry about that, and thanks for pointing this out!

[gregKeymaster]

Can you post your configuration file? (It should be located in /etc/dnschain/dnschain.conf).

[gregKeymaster]

no prob! And it's also recommended to pair DNSChain with a traditional resolver like PowerDNS.

There are some “bare bones” instructions on how to do that in this thread (in the first post).

Maybe someone will make a nice tutorial on how to do that at some point. 🙂

[gregKeymaster]

If it's running on a remote server then you need to make sure the port that it's running on is forwarded. You can do that by installing and setting up a package like ufw. Then you'd need to query it on its IP, not localhost. And if you want it to serve DNS to other computers, you'll need to either port map port 5333 to 53, or run it as root (not recommended) so that it can run on 53 directly.

For remote computers, you should also use systemd, and then run DNSChain via the included systemd unit file. Note that we've setup that file to do the port forwarding for you.

If you don't know what I'm talking about… I recommend doing some research on systemd and linux server admin. Feel free to post dnschain-specific questions here, and if you have general linux/debian questions, StackOverflow, Server Fault, or Ask Ubuntu might be a better places for that.

[gregKeymaster]

Yeah, it's running. If you have it running locally and on port 53, you can set your DNS to localhost (127.0.0.1) and visit okturtles.bit or namecoin.dns/d/okturtles.

If it's on port 5333, then you can test with a command like dig on linux (or on windows, via cygwin or other unix-like environment):

If you want to keep it running on port 5333, use dig like so:

Code:

-> % dig localhost -p 5333 okturtles.bit

; < <>> DiG 9.8.3-P1 < <>> localhost -p 5333 okturtles.bit
;; global options: +cmd
;; Got answer:
;; ->>HEADER< <- opcode: QUERY, status: NOERROR, id: 54155
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;localhost. IN A

;; ANSWER SECTION:
localhost. 86400 IN A 127.0.0.1

;; Query time: 63 msec
;; SERVER: 127.0.0.1#5333(127.0.0.1)
;; WHEN: Tue Sep 30 13:31:48 2014
;; MSG SIZE  rcvd: 43

;; Got answer:
;; ->>HEADER< <- opcode: QUERY, status: NOERROR, id: 918
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;okturtles.bit. IN A

;; ANSWER SECTION:
okturtles.bit. 600 IN A 192.184.93.146

;; Query time: 59 msec
;; SERVER: 127.0.0.1#5333(127.0.0.1)
;; WHEN: Tue Sep 30 13:31:48 2014
;; MSG SIZE  rcvd: 47

[gregKeymaster]

Hey crazyitalian,

That's a warning, and it telling you that in order to bind to port 53 it needs root/admin privileges. Since it doesn't have them it chose to bind to port 5333 which doesn't require admin privs.

[Author]

Posts