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"]}}}'
Code: Select all
zone "foo.bit" in {
type master;
file "/etc/bind/primary/db.foo";
};
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 ...."
Code: Select all
"@ IN SOA ..."
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!