Topic: [announce] Namecoin - a distributed naming system based on Bitcoin - page 84. (Read 596107 times)

What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?

Nothing? Since namecoin is a different dns system, the two can work together. Of course you need to tell your browser if the .bit address you are looking for is a namecoin one or a normal icann one.

That situation seems decidedly un-nothing-like to me, and awfully browser-centric.

As it currently stands, DNS resolver operators can add transparent support for the .bit space 'as if' it were the same as any other toplevel domain.
Scripts/email systems etc can then resolve .bit names without specific configuration.

The fact that ICANN may effectively yank this mode of operation out from under us (you can bet nearly all resolver operators will revert to resolving official ICANN names) is surely a risk which may make it hard to convince operators to support it in the first place.

Just make a plugin or something like that for the browser? You want to use namecoin dns, you activate the plugin and all addresses will be considered namecoin addresses.
Otherwise, well, normal ones.

You still seem to be being browser-centric. I have servers which don't even have a browser on them - and if .bit ever gains wider traction, I'd like them to be able to resolve .bit names. (for email, serverside api requests etc)
If various applications that might need to talk to your .bit domain need to be specifically configured or even reprogrammed - it greatly reduces the utility of the whole idea.

I guess it may still have some niche uses even if it's unable to be used in a properly integrated way with DNS - but I hope that as Khal suggests, the probability of ICANN allocating .bit to a registry is low.

Already I notice the situation with .bit domains is less than ideal in the chrome browser at least.
A non-existant .bit name is treated differently to a non-existant .com name.
A bogus .com name brings up the webpage not available screen indicating a DNS error, but if I put in a bogus .bit name - the chrome search feature is activated. Somehow under the covers chrome seems to treat .bit differently to other toplevel domains.

ehmdjii

sr. member

Activity: 351

Merit: 250

if i want mit dot bit domain to mirror or redirect to a regular dot com domain, what should i put in the map json?

Gabi

legendary

Activity: 1148

Merit: 1008

If you want to walk on water, get out of the boat

Quote from: marcus_of_augustus on November 17, 2011, 05:08:28 PM

What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?

Nothing? Since namecoin is a different dns system, the two can work together. Of course you need to tell your browser if the .bit address you are looking for is a namecoin one or a normal icann one.

That situation seems decidedly un-nothing-like to me, and awfully browser-centric.

As it currently stands, DNS resolver operators can add transparent support for the .bit space 'as if' it were the same as any other toplevel domain.
Scripts/email systems etc can then resolve .bit names without specific configuration.

The fact that ICANN may effectively yank this mode of operation out from under us (you can bet nearly all resolver operators will revert to resolving official ICANN names) is surely a risk which may make it hard to convince operators to support it in the first place.

Just make a plugin or something like that for the browser? You want to use namecoin dns, you activate the plugin and all addresses will be considered namecoin addresses.
Otherwise, well, normal ones.

khal

hero member

Activity: 540

Merit: 500

Quote from: bulanula on November 14, 2011, 01:50:25 PM

You guys need to hurry up :

-rescan functionality still not working
-wallet encryption not working
-GUI nowhere to be found
-alternate clients without TX fees requirement ?

They will be open for help I'm sure.

If you were a paying customer it may be different .... but you are not.

Indeed, help is welcome.
-rescan : what is your problem, this must work !?
-wallet encryption not working : of course, because the feature does not exist
-GUI nowhere to be found : Voicedotbit & NamecoinGUI, see : http://dot-bit.org/Tasks-NamecoinGUI
-alternate clients without TX fees requirement ? : Do you know you can force tx fees to 0 in bitcoin (search paytxfee) ? Same for namecoin ! What a revelation !

Quote from: julz on November 17, 2011, 06:09:37 PM

Because they're pretty much opening up arbitrary toplevel domains to whoever has deep enough pockets and the facilities to run a name registry.
The risk is that *someone* wants to run the .bit space, whether for its own sake, or to deliberately bring the space namecoin is trying to occupy back under control.
I have no real idea how likely that is - but the mere possibility makes .bit less attractive.

I guess there will be no real solution against that for .bit, but the probability is very low...
But, JohnDoe explained why we shouldn't worry (from: http://dot-bit.org/forum/viewtopic.php?p=1257#p1257) :

Quote from: JohnDoe

My opinion is that we shouldn't worry too much about it. Firstly this is only for very established companies, orgs and institutions. You need to pay 185k upfront with no security that your application will be accepted, and if it does you need to pay a yearly upkeep of 20k or something like that. To register a tld you need proof of ownership too (google can't register .apple) so with some help we could probably appeal a registration (there is a formal period for this in the registration process). It looks like a whole round of application takes quite a while, like a year or more, so if nobody tries to register .bit during the first round (applications close in February I think) then we would be able to gather quite a bit of evidence of prior use and possibly support from organizations like the EFF before the second round starts.

From our end we also have the advantage that .bit is in no way hardcoded (names are registered like d/name without the .bit tld) so it can be changed at will by the nameservers if there's a need for it. This further discourages people from shelling out 185k just to try to attack us.

Another solution would be to choose a second TLD that ICANN is not able to take. Something with 1 letter, with numbers ? I don't really know all the rules about that, so, help is welcome too.

julz

legendary

Activity: 1092

Merit: 1001

Quote from: marcus_of_augustus on November 17, 2011, 06:01:34 PM

What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?

Nothing? Since namecoin is a different dns system, the two can work together. Of course you need to tell your browser if the .bit address you are looking for is a namecoin one or a normal icann one.

That situation seems decidedly un-nothing-like to me, and awfully browser-centric.

As it currently stands, DNS resolver operators can add transparent support for the .bit space 'as if' it were the same as any other toplevel domain.
Scripts/email systems etc can then resolve .bit names without specific configuration.

The fact that ICANN may effectively yank this mode of operation out from under us (you can bet nearly all resolver operators will revert to resolving official ICANN names) is surely a risk which may make it hard to convince operators to support it in the first place.

Why would ICANN want to use .bit TLD in the first place ... see how much resistance they put up to extending beyond the limited set they began with. Adding in .bit for them would create more confusion than clarity. There is little upside for them to commandeer it at this stage. Why would they it is not like it is .com or .org ...

Because they're pretty much opening up arbitrary toplevel domains to whoever has deep enough pockets and the facilities to run a name registry.
The risk is that *someone* wants to run the .bit space, whether for its own sake, or to deliberately bring the space namecoin is trying to occupy back under control.
I have no real idea how likely that is - but the mere possibility makes .bit less attractive.

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?

Nothing? Since namecoin is a different dns system, the two can work together. Of course you need to tell your browser if the .bit address you are looking for is a namecoin one or a normal icann one.

That situation seems decidedly un-nothing-like to me, and awfully browser-centric.

As it currently stands, DNS resolver operators can add transparent support for the .bit space 'as if' it were the same as any other toplevel domain.
Scripts/email systems etc can then resolve .bit names without specific configuration.

The fact that ICANN may effectively yank this mode of operation out from under us (you can bet nearly all resolver operators will revert to resolving official ICANN names) is surely a risk which may make it hard to convince operators to support it in the first place.

Why would ICANN want to use .bit TLD in the first place ... see how much resistance they put up to extending beyond the limited set they began with. Adding in .bit for them would create more confusion than clarity. There is little upside for them to commandeer it at this stage. Why would they it is not like it is .com or .org ...

julz

legendary

Activity: 1092

Merit: 1001

Quote from: bulanula on November 14, 2011, 01:50:25 PM

What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?

Nothing? Since namecoin is a different dns system, the two can work together. Of course you need to tell your browser if the .bit address you are looking for is a namecoin one or a normal icann one.

That situation seems decidedly un-nothing-like to me, and awfully browser-centric.

As it currently stands, DNS resolver operators can add transparent support for the .bit space 'as if' it were the same as any other toplevel domain.
Scripts/email systems etc can then resolve .bit names without specific configuration.

The fact that ICANN may effectively yank this mode of operation out from under us (you can bet nearly all resolver operators will revert to resolving official ICANN names) is surely a risk which may make it hard to convince operators to support it in the first place.

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

You guys need to hurry up :

-rescan functionality still not working
-wallet encryption not working
-GUI nowhere to be found
-alternate clients without TX fees requirement ?

They will be open for help I'm sure.

If you were a paying customer it may be different .... but you are not.

bulanula

hero member

Activity: 518

Merit: 500

You guys need to hurry up :

-rescan functionality still not working
-wallet encryption not working
-GUI nowhere to be found
-alternate clients without TX fees requirement ?

Red Emerald

hero member

Activity: 742

Merit: 500

Quote from: khal on November 14, 2011, 11:56:16 AM

Quote from: Red Emerald on October 25, 2011, 07:06:32 PM

I already run my own DNS server for my own personal websites. I'll play around with the PHP->bind scripts over the next few days and let you know what I think.

Any news about your DNS server ?

I ended up just setting up a forward. My nameserver doesn't have PHP installed on it, as I'm playing with some other projects in python.

Code:

zone "bit" {
        type forward;
        forwarders {
                178.32.31.41; // French bit DNS
                78.47.86.43;  // German bit DNS
        };
};

It's an internal DNS, otherwise I'd publish the IP.

Gabi

legendary

Activity: 1148

Merit: 1008

If you want to walk on water, get out of the boat