实用商务经典模板16.pptVIP

IronHide Confidential DNS Protocol Overview Jack Mitchell Sr. Systems Engineer Infoblox jmitchell@ History of DNS Early networks relied on HOSTS.TXT (ARPANet ~200 hosts) Solution did not scale and DNS was proposed 1983 BIND was developed at Berkley 1986 (4.3 BSD) Internet Systems Consortium (ISC) now maintains BIND Infoblox creates DNS/DHCP Appliance 2000 The Yellow Pages for the Internet History of DNS Early networks relied on HOSTS.TXT (ARPANet ~200 hosts) Solution did not scale and DNS was proposed 1983 BIND was developed at Berkley 1986 (4.3 BSD) Internet Systems Consortium (ISC) now maintains BIND Infoblox creates DNS/DHCP Appliance 2000 The Yellow Pages for the Internet There’s more to it than that! How Hard can it be? Example: RRs in a zone file . 7200 IN SOA . . ( 2001061501 ; Serial 43200 ; Refresh 12 hours 14400 ; Retry 4 hours 345600 ; Expire 4 days 7200 ; Negative cache 2 hours ) . 7200 IN NS . . 7200 IN NS . . 3600 IN A 62 . 2600 IN A 5 DNS Described DNS is a data file And the protocol to access it (loads file when DNS starts) Designed for rapid lookup (queries) Replicated Content (primary – secondaries) Distributed Control (zones) DNS Ports Some Terms for DNS Domain Name Hierarchy Domains Zones Zones Related resource records are grouped into administrative units called zones Records that share the same ending are grouped together E.g., blox com and have in common To look at it another way, the namespace is broken into administrative units of zones Name servers load zero or more zones The zone data can come from a file, a database, or another name server A name server is authoritative for these zones It k