I did a zone transfer using dig of the .com .org and .edu spaces just after
NSI announced they were shutting down access (they left the f-root server
open for some strange reason) so I'd have a copy, and those zones are huge.
Plus, NSI long ago cut of FTP access, which would have made things a little
quicker than doing a query on all the .com address....
Submisison of entires:
Even though this was my initial arguement as to why we would have to
implement ANOTHER protocal anyways, it's not such a big deal. Many players
will not offer submission, and I suppose those that do can submit to a
central site though http or whatver which will then do the nightly or weekly
batch run, tearing it out of a relational DB to the zone files. For those
paying attention to Network Solutions method of doing business, why does
this sound so familiar :)...
Central control:
Been covered before and before...
August
-----Original Message-----
From: Andreas Bogk <andreas nospam at andreas.org>
To: cdindex nospam at freeamp.org <cdindex nospam at freeamp.org>
Date: Tuesday, March 09, 1999 4:26 PM
Subject: Re: Reality Check and Ideas
Alan Cox <alan nospam at redhat.com> writes:
> Ok my argument for DNS is this
Good arguments. Ok, then how would you solve the following problems:
- incremental replication of the whole database
- submission of entries
- central authorities (so who's going to be the primary for some subspace?
What if that server is temporarily unreachable?)
NNTP solves all that. It lacks some way to ensure consistency after
data loss at some site, though.
Andreas
-- "It is by caffeine alone I set my mind in motion. It is by the Beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion." -- National Lampoon's "Doon"