Who's up for creating a network of new gTLD servers? I'm sure it wouldn't be
too hard to reconstruct 90% of the com/net zones from publicly available
data (http://www.deleteddomains.com/newlist.shtml?cid=11673-11084 would be a
good start). Constantly farming for missed zones, and maybe even querying
the "real" servers for missing data. The updates would be a day or two
behind the "real" zones, but once you got a good number of eyeballs looking
to your servers instead of VeriSign's, you could probably convince quite a
few registrars to start sending you updates too.
I'm sure this breaks many an RFC, and has an unfathomable number of other
problems, but I see it this way: we can complain and whine about
mismanagement as much as we want, but until there is a viable alternative
available their will never be a change.
*hops into his fireproof undies* Comments anyone?
Date: Tue, 16 Sep 2003 11:07:41 -0700
From: Mike Damm
Who's up for creating a network of new gTLD servers? I'm sure
I dunno. We'd be trusting those operating the gTLD network. 
it wouldn't be too hard to reconstruct 90% of the com/net
zones from publicly available data
(http://www.deleteddomains.com/newlist.shtml?cid=11673-11084
It seems to think my Lynx browsing sessions are illegitimate, and
returns a nasty message.
would be a good start). Constantly farming for missed zones,
and maybe even querying the "real" servers for missing data.
The updates would be a day or two behind the "real" zones,
but once you got a good number of eyeballs looking to your
servers instead of VeriSign's, you could probably convince
quite a few registrars to start sending you updates too.
You're essentially having a resolver save cached domains, then
return responses.
I'm sure this breaks many an RFC, and has an unfathomable
number of other problems, but I see it this way: we can
*shrug*
Anycasting AS112 works well.
Eddy
This would require cooperation from the root-servers operators.
And a serious effort from ISP/NSP community to block network access to
root-servers that don't cooperate.
I agree that it's a good idea at this point. I see nothing else as a
serious long-term technical solution.
Mike Damm wrote:
You can download the real zones if you want easily enough. Some years ago
all this took was sending a few faxes.
> Who's up for creating a network of new gTLD servers?
This would require cooperation from the root-servers operators.
speaking for f-root, we won't be cooperating with anything like that.
we do not edit the zone files we serve. they come from iana, and if
you want something different served, you'll have to talk to iana. i
cannot speak for the other rootops but i suspect that their answers
might be compatible with, if not downright similar to, f-root's.
And a serious effort from ISP/NSP community to block network access to
root-servers that don't cooperate.
I agree that it's a good idea at this point. I see nothing else as a
serious long-term technical solution.
sounds like mob rule to me -- count me out. so, block me first, i guess?
Amen to that - the guys who run the *root* nameservers are not the problem.
They get DDoSed, and even when not DDoSed, 98% of the stuff thrown at them
is trash - and the servers keep going anyhow. The closest thing to a controversial
hijacking in like 20 years has been one test by Postel.
Yes, there's been issues with some TLDs regarding who the rightful registrar is,
but that's IANA's call not the root nameservers. And there's been issues with
the management of a TLD going bonzo in various ways - but again, that's not
the fault of the root itself.
Quite frankly, if the rest of the net ran as well and sanely as the guys
who run the root nameservers, we'd all have lots lower blood pressures...
speaking for f-root, we won't be cooperating with anything like that.
speaking for k-root we will not either.
... sounds like mob rule to me -- count me out. so, block me first, i guess?
block us second.
Daniel