Welcome to WebmasterWorld Guest from 23.20.25.122

Forum Moderators: buckworks & webwork

ICANN Says .corp, .home, .mail Proposing Never to Release as TLDs

     
11:13 am on Feb 13, 2018 (gmt 0)

Senior Member from US 

WebmasterWorld Senior Member tangor is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Nov 29, 2005
posts:8459
votes: 652


You will never be able to own an official .home, .mail or .corp domain name or email address on the public internet.

It means if you have machines called things like storage.home or buildserver.corp on your home or private business network, you can be sure no one will be able to buy domains like storage.home or buildserver.corp, thus sparing you the messy situation of client PCs accidentally connecting to the wrong box, depending on their DNS settings.

It's bad news for phishers and other miscreants, and a relief for network managers.

The decision to axe the trio of dot-words from the public 'net was finally reached by domain-name system overseer ICANN at a recent board meeting, six years after 20 companies paid the organization $185,000 apiece to get hold of the online real estate.


[theregister.co.uk...]

Works for me! Just surprised it took six years to figure this out.
2:01 pm on Feb 13, 2018 (gmt 0)

Moderator This Forum

WebmasterWorld Administrator webwork is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:June 2, 2003
posts:8009
votes: 70


Fascinating. I guess there's never a sufficient supply of easy targets for miscreants.

Thanks for the find. It really is interesting, in a who woulda thunk it way:

The three dot-words have been officially banned as top-level domains because of the widespread conflicts that DNS experts are certain would result if they were added to the public internet: all three words are used extensively by sysadmins, webmasters, and tech geeks for testing and other systems on internal networks.


Network Managers and Systems Administrators know ^this^ to be true from past domain experience. #justsayin #sezthemiscreant #argh #reallyimagoodguy #arghwhimperslitheraway
12:40 pm on Feb 14, 2018 (gmt 0)

Senior Member from GB 

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month

joined:Nov 16, 2005
posts:2773
votes: 112


Does .local have a special status too?
1:04 pm on Feb 15, 2018 (gmt 0)

New User from US 

joined:July 11, 2017
posts:4
votes: 0


They should have used this logic for .host
10:16 pm on Feb 15, 2018 (gmt 0)

Moderator from GB 

WebmasterWorld Administrator mack is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:June 15, 2001
posts:7746
votes: 50


Let's hope system admins use these blocked words now for networking so as not to run the risk of being caught out in the future.

Mack.
12:42 pm on Feb 17, 2018 (gmt 0)

Senior Member from GB 

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month

joined:Nov 16, 2005
posts:2773
votes: 112


Does anyone know what happens when you have both local multicast DNS and whatever-you-call-namesever-provided-DNS available for a domain which takes priority? Does it depend on OS or is there a standard?
11:33 pm on Mar 11, 2018 (gmt 0)

Moderator from GB 

WebmasterWorld Administrator mack is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:June 15, 2001
posts:7746
votes: 50


I think the local DNS would take property Graeme because it would not make it out into the wider network.

Mack.