5 ms·

Namespaces exist for a reason. For example, what do you call your network printer after http://canon http://canon gets reserved by the printer manufacturer? Sam

Namespaces exist for a reason. For example, what do you call your network printer after http://canon http://canon gets reserved by the printer manufacturer? Same with http://epson http://epson, whatever. And is http://printer1/ http://printer1/ safe? Only until someone writes a paragraph justification and shows up with $1m. The entire process is a money grabbing farce.

icebraining 14y ago
http://en.wikipedia.org/wiki/.local http://en.wikipedia.org/wiki/.local
- Chlorus 14y ago
  .local causes chaos if you're running Bonjour/Avahi on the same network
  - icebraining 14y ago
    You just need to configure them as static mappings in /etc/avahi/hosts. http://linux.die.net/man/5/avahi.hosts http://linux.die.net/man/5/avahi.hosts
- forgotusername 14y ago
  Why should I have to type "canon.local" for my printer name, just in order to avoid an advert to buy a new printer? This destroys any sense of user preference in favor of large corporations pushing their shit further into your face even when you explicitly don't want it. I've worked at many places where http://search/ http://search/ was the Intranet search facility. Not now though, nope. Now your IT department will be under pressure to accept Big Search's latest site-integrated intranet search which they conveniently started marketing around the time they broke all your local URLs.
  - nikcub 14y ago
    The good thing about DNS is that the user controls it. You can set it to whatever you want. Enough people set it one way and it becomes a standard that no board can decide against.
    - because 14y ago
      Exactly. What's needed is more public education. DNS is a basic thing all users should know about. You can stop someone on the street and they will know what "RAM" is. They might not be able to explain how it works or what it stands for, but they know what it is and they know they need it for applications to run smoothly. Same should be true of DNS. Mozilla, not to mention Adobe, can coordinate millions of people to all download the same program (Firefox, Flash plugin). People can be taught how to control their own DNS, e.g. how to choose a DNS server. But ICANN likes users to remain ignorant. They want everyone to use their root server without ever thinking about it. Well, that server is about to become overrun with needless tld's.
      - icebraining 14y ago
        You can stop someone on the street and they will know what "RAM" is. People in NY were asked what their browser was and the most common reply was "Google" - and this was before Chrome had any kind of share. People are completely ignorant when it comes to technology.
        because 14y ago
        I saw that video. Hilarious! But you're wrong. When people go to buy a computer, most know what RAM is, i.e., they've heard of it. It's because advertisements always mention it.
    - pooriaazimi 14y ago
      Sometimes changing DNS servers causes biiiig (and confusing) problems with captive networks.
ejdyksen 14y ago
Does owning a gTLD entitle you to use the top of your namespace for anything other than NS/SOA records? Put another way, if I'm Microsoft, can I put my website at http://microsoft http://microsoft? Or do I have to use http://www.microsoft http://www.microsoft? I've looked to see if there is a policy from ICANN on this, but I can't find one. Historically, TLDs did not themselves point to hosts (or have other things like MX or TXT records).
- icebraining 14y ago
  Some ccTLDs do have A records, though, like http://ac http://ac
  - franze 14y ago
    great example!!! i just tried to submit http://ac/ to hackernews. guess what? it didn't work.
    - Sami_Lehtinen 14y ago
      Yeah, it's common to have bad url or email address validation. Many sites do not accept short email addresses at all. As example a @bc.de (space is there intentionally). When it becomes a @ bc then it's interesting to see how many sites will fail with that.
    - because 14y ago
      What browser are you using? This worked in my browser.
    - Cyranix 14y ago
      I believe that TLDs with A records should resolve correctly if you add a period to the end, as in "http://ac. http://ac.. As I recall, this came up when the "http://to. http://to. link shortener [no longer available] was discussed a while ago.
  - ajasmin 14y ago
    With the current trend of combining the address and search bar I doubt browsers will let you go to e.g. http://lol http://lol when you type "lol" in the bar. In fact I just checked that typing "ac" in the Chrome omnibox makes a Google search for "ac" as I would expect. So the value of having an A record on a TLD is limited. Edit: Somehow I missed the bar on top of the search results that says "Did you mean to go to http://ac http://ac " so there's some value after all.

icebraining 14y ago

http://en.wikipedia.org/wiki/.local http://en.wikipedia.org/wiki/.local

Chlorus 14y ago
.local causes chaos if you're running Bonjour/Avahi on the same network
- icebraining 14y ago
  You just need to configure them as static mappings in /etc/avahi/hosts. http://linux.die.net/man/5/avahi.hosts http://linux.die.net/man/5/avahi.hosts
forgotusername 14y ago
Why should I have to type "canon.local" for my printer name, just in order to avoid an advert to buy a new printer? This destroys any sense of user preference in favor of large corporations pushing their shit further into your face even when you explicitly don't want it. I've worked at many places where http://search/ http://search/ was the Intranet search facility. Not now though, nope. Now your IT department will be under pressure to accept Big Search's latest site-integrated intranet search which they conveniently started marketing around the time they broke all your local URLs.
- nikcub 14y ago
  The good thing about DNS is that the user controls it. You can set it to whatever you want. Enough people set it one way and it becomes a standard that no board can decide against.
  - because 14y ago
    Exactly. What's needed is more public education. DNS is a basic thing all users should know about. You can stop someone on the street and they will know what "RAM" is. They might not be able to explain how it works or what it stands for, but they know what it is and they know they need it for applications to run smoothly. Same should be true of DNS. Mozilla, not to mention Adobe, can coordinate millions of people to all download the same program (Firefox, Flash plugin). People can be taught how to control their own DNS, e.g. how to choose a DNS server. But ICANN likes users to remain ignorant. They want everyone to use their root server without ever thinking about it. Well, that server is about to become overrun with needless tld's.
    - icebraining 14y ago
      You can stop someone on the street and they will know what "RAM" is. People in NY were asked what their browser was and the most common reply was "Google" - and this was before Chrome had any kind of share. People are completely ignorant when it comes to technology.
      - because 14y ago
        I saw that video. Hilarious! But you're wrong. When people go to buy a computer, most know what RAM is, i.e., they've heard of it. It's because advertisements always mention it.
  - pooriaazimi 14y ago
    Sometimes changing DNS servers causes biiiig (and confusing) problems with captive networks.

ejdyksen 14y ago

Does owning a gTLD entitle you to use the top of your namespace for anything other than NS/SOA records? Put another way, if I'm Microsoft, can I put my website at http://microsoft http://microsoft? Or do I have to use http://www.microsoft http://www.microsoft? I've looked to see if there is a policy from ICANN on this, but I can't find one. Historically, TLDs did not themselves point to hosts (or have other things like MX or TXT records).

icebraining 14y ago
Some ccTLDs do have A records, though, like http://ac http://ac
- franze 14y ago
  great example!!! i just tried to submit http://ac/ to hackernews. guess what? it didn't work.
  - Sami_Lehtinen 14y ago
    Yeah, it's common to have bad url or email address validation. Many sites do not accept short email addresses at all. As example a @bc.de (space is there intentionally). When it becomes a @ bc then it's interesting to see how many sites will fail with that.
  - because 14y ago
    What browser are you using? This worked in my browser.
  - Cyranix 14y ago
    I believe that TLDs with A records should resolve correctly if you add a period to the end, as in "http://ac. http://ac.. As I recall, this came up when the "http://to. http://to. link shortener [no longer available] was discussed a while ago.
- ajasmin 14y ago
  With the current trend of combining the address and search bar I doubt browsers will let you go to e.g. http://lol http://lol when you type "lol" in the bar. In fact I just checked that typing "ac" in the Chrome omnibox makes a Google search for "ac" as I would expect. So the value of having an A record on a TLD is limited. Edit: Somehow I missed the bar on top of the search results that says "Did you mean to go to http://ac http://ac " so there's some value after all.