Namecoin Forum

micah wrote:I've got a domain name that is currently registered with an ICANN-cabal approved registrar, that I am acting as the primary and secondary nameserver for. I registered the same name in the namecoin universe and I configured the .bit nameservers to point to my already existing nameservers so I could just serve up the same zone information for the .bit domain as I am with the original ICANN domain.

However, this didn't work out of the box, because my nameservers did not know about the .bit zone and needed to be configured to recognize and respond to it. This is how I did this.

First you need to update your namecoin name to map the nameservers to your nameservers. Lets say my original domain name was "foo.net" and I registered "foo.bit"

Code: Select all

../namecoind name_update d/foo '{"map":{"":{"ns":["YOUR.NAME.SERVER1","YOUR.NAMESERVER2"]}}}'

Then you must configure your bind's named.conf (or named.conf.local if you are using Debian or a Debian derived distro) to recognize the domain:

Code: Select all

zone "foo.bit" in {
  type master;
  file "/etc/bind/primary/db.foo";
};

You should point the file directive to the zone file that "yourname.net" also points to.

Then you need to make sure that "db.yourname" is using RFC 1035 global SOA directive synthesis. In otherwords, if your SOA record says:

Code: Select all

"foo.net   IN   SOA ...." 

then you want to change it to:

Code: Select all

"@    IN   SOA ..."

(dont forget to bump the serial number, and restart bind!)

The @ will be substituted with an $ORIGIN synthesis based on the value of the zone name in the named.conf file.

Now foo.net subdomains and records will be resolved as they always were, and foo.bit will do the exact same thing. No need to manage two different files with the exact same content!

I've got a domain name that is currently registered with an ICANN-cabal approved registrar, that I am acting as the primary and secondary nameserver for. I registered the same name in the namecoin universe and I configured the .bit nameservers to point to my already existing nameservers so I could just serve up the same zone information for the .bit domain as I am with the original ICANN domain.

doublec wrote:I'm curious why you'd want to point your namecoin domain name to the existing DNS?

Why not code the IP address into the namecoin domain value? This way you're protected from someone manipulating the DNS entry.

namecoind name_firstupdate d/myname <rand> <tx> '{"map": {"": {"ns": ["198.7.0.1", "198.7.0.2"]} } }'

khal wrote:

Code: Select all

'{"ip": ["166.84.62.124","166.84.62.252"], "map":{"": "166.84.62.124"}}'

namecoind name_update d/watchpocket <rand> '{"ip": ["166.84.62.124","166.84.62.252"], "map":{"": "166.84.62.124"}}'

host watchpocket.bit 166.84.62.252 
Using domain server:
Name: 178.32.31.41
Address: 178.32.31.41#53
Aliases: 

Host watchpocket.bit not found: 3(NXDOMAIN)

"Value: {invalid)"

This one requires you to configure apache only.

khal wrote:You'll need to configure this right on your server :p