The Domain Name System ITU域名系统国际电信联盟.pptVIP

A Quick Introduction to the Domain Name System David Conrad david.conrad@ Chief Technology Officer Overview Introduction to the DNS DNS Components DNS Structure and Hierarchy The DNS in Context The DNS is… The “Domain Name System” Created in 1983 by Paul Mockapetris (RFCs 1034 and 1035), modified, updated, and enhanced by a myriad of subsequent RFCs What Internet users use to reference anything by name on the Internet The mechanism by which Internet software translates names to addresses and vice versa A Quick Digression:Names versus Addresses An address is how you get to an endpoint Typically, hierarchical (for scaling): 950 Charter Street, Redwood City CA, 94063 1, +1-650-381-6003 A “name” is how an endpoint is referenced Typically, no structurally significant hierarchy “David”, “Tokyo”, “” The DNS is also… A lookup mechanism for translating objects into other objects A globally distributed, loosely coherent, scalable, reliable, dynamic database Comprised of three components A “name space” Servers making that name space available Resolvers (clients) which query the servers about the name space DNS as a Lookup Mechanism Users generally prefer names to numbers Computers prefer numbers to names DNS provides the mapping between the two I have “x”, give me “y” DNS is NOT a directory service No way to search the database No easy way to add this functionality DNS as a Database Keys to the database are “domain names” , 18., 6.4. Over 100,000,000 domain names stored Each domain name contains one or more attributes Known as “resource records” Each attribute individually retrievable Global Distribution Data is maintained locally, but retrievable globally No single computer has all DNS data DNS lookups can be performed by any device Remote DNS data is locally cachable to improve performance Loose Coherency The database is always internally consistent Each version of a subset of the database (a zone) has a serial number The serial number is incremented on each database chang