On Sun, Jun 19, 2011 at 08:22:17PM -0400, Jay Ashworth wrote:
----- Original Message -----
From: "Paul Vixie" <vixie@isc.org>
inevitably there will be folks who register .FOOBAR and advertise it as "http://foobar/" on a billboard and then get burned by all of the local "foobar.this.tld" and "foobar.that.tld" names that will get reached instead of their TLD. i say inevitable; i don't know a way to avoid it since there will be a lot of money and a lot of people involved.
I think it's probably worse than that, since a lot of the companies who might be foolish enough to try that *are companies that make stuff that's on your LAN*... and what are you going to name the *one* Apple server that's on your LAN in your internal DNS?
Of course; you're gonna call it "apple".
And it only gets better from there... how many places have various "cutesy" naming schemes that might include one or more trademarks (or whatever) that someone might want as a TLD? A naming scheme involving fruit would cover your "apple" example, but I'd bet that someone, somewhere, names their servers after fast food restaurants or brands of shoe... and I'm confident in predicting that there are plenty of cartoon characters that some company or another will want to turn into a TLD. - Matt -- When all you have is a nailgun, every problem looks like a messiah. -- Iain Chalmers, ASR