[mootothemax]

Is there a default domain for these tlds? Let's take .home for example. How will this work when typing it into a browser?

I believe it's possible to set things up so that "home" or "co.uk" on their own will work. As below, my memory is hazy, and I have no idea how many RFCs this behaviour might violate, but I certainly remember us doing so.

My background: many, many years ago, I used to work for a minor country-code tld, and we set up fun email addresses such as: a@cctld or t@cctld (for Tom ;-)). My memory is hazy, but I think this violates some RFC somewhere. Mail still got delivered, though.

[freehunter]

This would be tricky for LANs. I'm not sure too many corporate network admins would be happy with the amount of work they'd have to do to change up all the DNS entries when "test" no longer routes to "test.company.com" while you're on the company.com domain. You'd have a riot when the development staff has to take a couple weeks to change over all their pathnames.

I'm of the opinion that RFCs don't matter if they're not being enforced. What matters is the implementation that exists in the real world. It doesn't matter what the ITU says 4G is supposed to be when 4G already implemented as something completely different. What would make sense is www.home routing to the default .home domain.

[omh]

It wouldn't be quite such a big problem, since well-behaved clients should attempt to use 'home.company.com' before the root 'home'. Regardless of what is possible or allowed by RFCs, that behaviour should discourage TLD holders from trying to use a naked 'home', since a lot of users wouldn't be able to access it.

[andrewheins]

See, that's really interesting. I wonder if that's been patched since then.

It just seems weird to have a tld absent a host.

[rfugger]

I should have applied for .localhost.