North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Re: I've just tried new.net's plugin. Don't.
- From: Aaron Hopkins
- Date: Fri Mar 16 23:52:05 2001
-----BEGIN PGP SIGNED MESSAGE-----
> So the plug-in does *not* change which dns server you query.
> if a query fails against your normal name server it
> just appends .newdotnet.net or, if that fails, makes stuff up.
This is a decent description of how the client is currently working, except
that it appends .new.net on to the end.
When the resolver plugin can't resolve a domain, it offers up the IP of a
web site that explains that the domain doesn't exist. This also contains
framed Google results and was an experiment with improving the user
experience. A wildcard was specifically not added to the root zone to
attempt to avoid some issues.
As has been pointed out on NANOG, this may cause more problems than its
worth, specifically for non-browser applications. In the next update to the
client, this feature will be removed. This should happen in a week or so.
There will still be wildcards in the new.net TLDs. We did this for *.tv
when we launched DotTV, and I'm not aware of significant problems with it.
Even though this isn't in place for *.com, the typo-squatters catch the
common mistakes anyway; DotTV and new.net at least also provide MX records
that immediately bounce all mail.
Should anyone be interested in offering more direct feedback about the
specifics of the implementation of this project than to NANOG, please feel
free to mail firstname.lastname@example.org. There will also shortly be mailing lists
available for announcements and discussion.
Systems Engineer, idealab!
Acting VP of Engineering, new.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----