I removed the plug-in already, but pinging www.pie.shop went like this: ping www.pie.shop std query for www.pie.shop against my name server fails std query for www.pie.shop.computerjobs.com against my name server failes wins query for www.pie.shop fails netbios broadcast for www.pie.shop fails x1 netbios broadcast for www.pie.shop fails x2 netbios broadcast for www.pie.shop fails x3 std query for www.pie.shop against my name server fails std query for www.pie.shop.computerjobs.com against my name server failes wins query for www.pie.shop fails netbios broadcast for www.pie.shop fails x1 netbios broadcast for www.pie.shop fails x2 netbios broadcast for www.pie.shop fails x3 std query for www.pie.shop.newdotnet.net against my name server newdotnet's NS replied with the IP for www.pie.shop.newdotnet.net & the echos came back. I did mean to say in my last posting, everything *non-resolvable* outside the ICANN TLD's is resolved to 64.208.49.135 Existing new.net TLD domains resolve to whatever their IPs are. The plug-in, however, sends ANY query outside the ICANN TLDs to 64.208.49.135. This usurps any and every other imaginable future TLD, ie www.bull.shit They're not advertising a 'shit' domain (um, literally), and yet requests for 'shit' go to their NS. Their scheme, if successful, takes over service for EVERY TLD domain not already in operation by ICANN. Who's the monopoly? -----Original Message----- From: Kevin Loch [mailto:kloch@opnsys.com] Sent: Wednesday, March 14, 2001 5:57 PM To: Chris Davis; nanog@merit.edu Subject: Re: I've just tried new.net's plugin. Don't. Chris Davis wrote:
I downloaded their plug-in and then:
What happens when you ping www.pie.shop which is in a new.net "private" TLD? (snip)
Seems that everything in the world not ending with an ICANN TLD goes to 64.208.49.135. Have a look at http://64.208.49.135
That was probably meant to be somewhat meaningfull with names and not IP numbers. BTW, do you mean "everything not ending with an ICANN TLD or "everything not resolvable"? (see above) KL