It appears as if Michael S. Lorrey wrote:
|The entire DNS database is updated regularly on every web server at
|every ISP, so there is not threat to its being destroyed. Thats why they
|are called name servers. When you request a page from a site, your ISP's
|webserver looks up the DNS and its corresponding IP address, then
|queries the network for the data from that IP address. The routers take
|that query and send it to the next closer router, etc. The system does
|not query network solutions' registry every time.
The DNS (Domain Name System) data is distributed over the whole Internet, and there exists no "entire DNS database", except in the mind of the abstractor.
You could, in theory, ask every DNS server for a copy of their data base, and
make a single data base of the data. In practices, however, the can be
(a) the data would be stale and incomplete at the same time:
the data change all the time everywhere. (b) the data base would require very large amounts of memory to store. (c) the bandwidth to copy it to your node would be enormous.
It appears as if Alejandro Dubrovsky <email@example.com> commented:
|Each DNS at each ISP holds a minuscule share of the entire database, most
|definitely not the entire database. It can cache requests that go through
|it but that only for a short time (usually one hour) and only of the
|request done on it. A DNS usually only holds the IP table for whatever
|domains it is acting as a master or as a secondary for, and usually you
|only have two servers knowing the IPs for a subdomain. Whatever ISP you
|are using does not have a clue what IP corresponds to
|s335984.student.uq.edu.au but the root servers know who the dns master for
|edu.au is (munnari.oz.au), who still doesn't know the ip but it knows that
|the master dns for uq.edu.au is krefti.uq.edu.au, and so on. This system
|enables each dns to respond quickly to name lookups since they only have
|to hold a couple of name to ip matchings but it does mean that it is
|fragile. If the 7 or 8 root servers were taken down all cross domain
|lookups (eg from .edu to .com, or from .gov to .uk) would fail after the
|corresponding caches expire (1 to 3 hours).
On May 1, 1999, there existed 13 root servers:
Name IP number Location
A.ROOT-SERVERS.NET 126.96.36.199 InterNIC (NSI) - USA B.ROOT-SERVERS.NET 188.8.131.52 Information Sciences Institute, University of Southern California - USA C.ROOT-SERVERS.NET 184.108.40.206 PSINet, Inc. - USA D.ROOT-SERVERS.NET 220.127.116.11 University of Maryland - USA E.ROOT-SERVERS.NET 18.104.22.168 NASA - USA F.ROOT-SERVERS.NET 22.214.171.124 Internet Software Consortium - USA? G.ROOT-SERVERS.NET 126.96.36.199 Network Information Center - USA H.ROOT-SERVERS.NET 188.8.131.52 U.S. Army Research Laboratory, Maryland - USA I.ROOT-SERVERS.NET 184.108.40.206 NORDUnet - Scandinavia J.ROOT-SERVERS.NET 220.127.116.11 InterNIC (NSI) - USA K.ROOT-SERVERS.NET 18.104.22.168 RIPE Network Coordination Centre (NCC) Amsterdam - Netherlands L.ROOT-SERVERS.NET 22.214.171.124 ISI (IANA) - USA M.ROOT-SERVERS.NET 126.96.36.199 Widely Integrated Distributed Environment (WIDE) - Japan
A list of the current DNS root servers can be acquired from <URL:ftp://RS.INTERNIC.NET/domain/named.root>, which might be a good idea for all DNS server administrators to do now and then.