Post by jonz Post by Keith Keller
It is truly frightening that some people are allowed to register
OK, I'll bite with the obvious question. What is your alternative?
That's a good question, and one for which I don't have a good answer.
Ideally, only people who actually know what domain registration (and
DNS) entails, from a high-level technical perspective, should be
permitted to register a domain. So they don't necessarily need to know
the details of actually running a BIND server, but they should at least
know the rules for e.g. how many servers are required, what DNS records
are required for a minimal zone file. Perhaps they could also be
required to update their individual whois records. It used to be that
contacts were references to domain handles, so that as long as your
individual handle was up to date, you wouldn't have to update every
domain for which you were responsible. I don't know if that exists any
Another possibility might be to enforce penalties if a user doesn't
update his whois records. For example, if I leave my organization, but
don't pass on my domain responsibilities to someone else in the
organization, perhaps I have to pay a penalty. A successful pass-off of
responsibility would entail the new person explicitly accepting
responsibility of the domain; I couldn't just silently update the
records and make up a name that goes nowhere.
I suspect that most nontechnical people would protest many of these
measures. They would rather people be able to register domains easily,
and the fact that many people will screw up their domains doesn't
matter. I can actually understand that viewpoint; it's a
democratization of domain registration that is certainly desirable. So
I don't know how to address their concerns while still keeping domain
registration limited to people who know what they're doing.
(try just my userid to email me)
see X- headers for PGP signature information