martinisky said:
This smells like confusion and dilution to me. The more you dilute extension names it seems the more .com will remain king especially because people will be so confused with dots being placed everywhere..... And in fact i think it smells mostly of greed by icaan. Why would Coke need to have a .cola extension when they could have any website they want with *****.coke.com?
IMO the only real thing that will hurt .com would be if there was an extension that didnt have an extension! you want to go to Coke's website? Type in coke, thats it. no more need for .com .net .stupidextensionnamehere. But that will never happen because then they'd eventually run out of things to sell. Just like the fact that there have been lightbulbs that will burn basically forever but no one will release them because they want you to keep buying. They want you to buy it so it will burn out and you can buy it again. Strange analogy maybe but hopefully it makes my point. Consumption is what they want.
Either way the future of domaining and the net is going to be very intersting and i just hope the great group of people here in the namepros community can work together to take advantage of wherever the future may take us! Good luck to you all! I hope we can make some profits and have some fun together!
:wave:
The dns system is by design a hierarchical distributed database. What that means is that during dns resolution, the process begins at the end with the implied "." (dot).
Try this experiment:
http://www.namepros.com./
http://www.namepros.com./domain-name-discussion/
Notice the "." after the com? That is the implied address of the root servers. Basically, the root servers (.) point to the tld servers for .com, .net, and all other .gtld and .cctld. Then the tld servers point to the second level domains, like namepros. This is done at higher levels of the namespace hierarchy too. So resolution goes like this:
. (find the root servers)
com (get com address from root servers)
namepros (get namepros address from the com tld server)
...etc...
This makes the dns system scalable, and ensures reasonable performance. Now suppose that we flatten the entire namespace and remove the hierarchy... i.e., suppose we just let
http://coke resolve as-is. First of all, that is entirely possible, but not smart. I have even set up things like this in the "alternate root" for fun, and had alt-root tld's resolve to a web page. The reason that it is possible but "not smart" is that it would force a lot of traffic directly onto the root servers (a bad thing). It sounds nice, but the solution is not scalable.