-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The first and most obvious thing - that should be done NOW - is : If a domain name doesn't resolve, DON'T REDIRECT IT!!! At the very least put up a page explaining this to the user and give them the OPTION of going to the google page... Don't make it automatic and seamless... Don't even let the user opt to make it automatic, they NEED to know that they misspelled the name. Tim
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Simon Higgs Sent: Wednesday, March 14, 2001 23:34 To: Randy Bush Cc: nanog@merit.edu Subject: RE: I've just tried new.net's plugin. Don't.
At 06:54 PM 3/14/01 -0800, you wrote:
This is the exact scenario that I envision happening and have been complaining about. My operations and tech support staff will become bogged down in this mess, probably to the extent that I have to augment staff. Add in the phone bill and other overhead costs... Suddenly I'm paying out a LOT of money just so a bunch of VCs can make a money grab.
you get the pain, they get the pay. cool scam, eh?
So what practical steps does New.net need to take to reduce the load on the help desks? Going out of business, getting rid of the dumb plug-in, and using a proper root server network have already been suggested. What else would help minimize the load on the network help desks?
I'll be taking real world solutions that can be offered here to the New.Net CEO myself.
Don't bother to complain if you're not prepared to be part of the solution.
Thanks &
Best Regards,
Simon Higgs
-- It's a feature not a bug...
-----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> iQA/AwUBOrDXKxRIXzEQLahvEQIW8gCg+KSwL663Wx5x1zBxEageVguZltAAn1ka ygEH9qjdCLan2A41lPf2G5x5 =MEbD -----END PGP SIGNATURE-----