On Fri, 2010-08-06 at 20:28 -0700, Tim wrote: > > There seem be three options roughly: > > > > 1) Use .foo TLD which isn't used on the Internet ( dangerous ). > > > > 2) Use globally registered domain name ( wasteful ). > > > > 3) Use a subdomain of a globally registered domain name ( limiting ). > > > No, there's a fourth option. Use "split horizon" DNS: > http://en.wikipedia.org/wiki/Split-horizon_DNS
I use split horizon DNS, good point. I like .pri as a TLD for a private network. I can't tell though if pri is a global TLD or not. I suppose I could use my registered domain name instead of ending private addresses with pri. I actually use my global domain name on most of my wired private hosts. As far as the this is a solution looking for a problem comment. No. There is a desire in the world today to use the same name for different web sites. What I am proposing is that a scope field be added to domain names as a separate text field. You don't type this in, another mechanism allows choosing the correct scope indicator from a list. The scopes would include local, Internet, USA, UK (England), DE (Germany), etcetera. The point of scoping every Internet domain name is to permit the usage of any name on a local network and the usage of popular names more than once for different public web sites. What I foresee is a drop down menu that starts out with a country code for every single country plus local and Internet (everywhere). The default is of course Internet where a list of choices becomes highlighted when there is a collision. As far as claims that there is no problem, that is a bunch of bull. No matter how many bits there are to represent computers on the Internet, there are only so many names that people are going to want to type in. Why should someone in England be prevented from registering a robinson.org domain because someone elsewhere in the world already has? There are numerous Robinson families in the world. As I understand the current system, if I register robinson.org, that means that nobody else in the world can use robinson.org until I give the name up. Don't tell me that the global name space can't be expanded by use of another label. A possible benefit of my proposal is that you can say which region you want your searches to target potentially improving your hit ratio. If the geographic labels are accurate, you can use them to cut down on spam perhaps as well. Privacy advocates obviously are going to hate this, but was the purpose and intent of the Internet to make the whole world seem like one place where you can't tell where anything is coming from? Consumers of the Internet want to influence what they consume. A robust naming system that can give answers based on regions seems expedient. If the region you want to check out is your local network, wouldn't it be nice to have any name you want to use at your fingertips? The current domain system doesn't allow me to create a local http://www.ebay.com/ that won't block the global one. That may seem like a lame example, but the risk of pri becoming an Internet TLD is real. There are arguments that RFC1918 was a bad idea because companies merge and their IP address space conflicts. Well, Dynamic DNS should solve that problem. I assign RFC 1918 addresses statically via DHCP, which is an oxymoron. If I could assign from a pool of IP addresses and send the MAC address and assigned IP address as well as requested host name to a DNS server and dynamically generate a zone file, I'd never have a collision problem. There is limited unique address space even if you get an IPv6 block, so solving the problem of collisions by having everyone use global IP blocks is not practical. One problem I face for network root, how do I update the hosts file if I'm doing dynamic dns? _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
