DNS : Domain Name System

Slides:



Advertisements
Similar presentations
Domain Name System. DNS is a client/server protocol which provides Name to IP Address Resolution.
Advertisements

1 DNS. 2 BIND DNS –Resolve names to IP address –Resolve IP address to names (reverse DNS) BIND –Berkeley Internet Name Domain system Version 4 is still.
The Domain Name System. CeylonLinux DNS concepts using BIND 2 Hostnames IP Addresses are great for computers –IP address includes information used for.
Domain Name System (DNS) Network Information Center (NIC) : HOSTS.TXT.
Domain Name System: DNS
TCP/IP Protocol Suite 1 Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Chapter 19 Domain Name System (DNS)
25.1 Chapter 25 Domain Name System Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Domain Name System ( DNS )  DNS is the system that provides name to address mapping for the internet.
TCP/IP Protocol Suite 1 Chapter 17 Upon completion you will be able to: Domain Name System: DNS Understand how the DNS is organized Know the domains in.
Presented by Neeta Jain CISC 856 TCP/IP and Upper Layer Protocols RFC 1034 & RFC 1035.
Module 12: Domain Name System (DNS)
NET0183 Networks and Communications Lecture 25 DNS Domain Name System 8/25/20091 NET0183 Networks and Communications by Dr Andy Brooks.
Netprog: DNS and name lookups1 Address Conversion Functions and The Domain Name System Refs: Chapter 9 RFC 1034 RFC 1035.
Domain Names System The Domain Name System (DNS) is a hierarchical distributed naming system for computers, services, or any resource connected to the.
Microsoft Windows Server 2003 TCP/IP Protocols and Services Technical Reference Slide: 1 Lesson 17 Domain Name System (DNS)
DNS: Domain Name System
25.1 Chapter 25 Domain Name System Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
14 DNS : The Domain Name System. 14 Introduction - Problem Computers are used to work with numbers Humans are used to work with names ==> IP addresses.
McGraw-Hill©The McGraw-Hill Companies, Inc., 2000 Network Protocols Chapter 25 (Data Communication & Networking Book): Domain Name System (DNS) 1.
Chapter 17 Domain Name System
25.1 Chapter 25 Domain Name System Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Chapter 29 Domain Name System (DNS) Allows users to reference computer names via symbolic names translates symbolic host names into associated IP addresses.
TCP/IP Protocol Suite 1 Chapter 17 Upon completion you will be able to: Domain Name System: DNS Understand how the DNS is organized Know the domains in.
Domain Name System CH 25 Aseel Alturki
October 8, 2015 University of Tulsa - Center for Information Security Microsoft Windows 2000 DNS October 8, 2015.
Netprog: DNS and name lookups1 Address Conversion Functions and The Domain Name System Refs: Chapter 9 RFC 1034 RFC 1035.
Internet and Intranet Protocols and Applications Lecture 5 Application Protocols: DNS February 20, 2002 Joseph Conron Computer Science Department New York.
1 Kyung Hee University Chapter 18 Domain Name System.
Domain Name System Refs: Chapter 9 RFC 1034 RFC 1035.
CPSC 441: DNS 1. DNS: Domain Name System Internet hosts: m IP address (32 bit) - used for addressing datagrams m “name”, e.g., - used by.
Domain Name System (DNS). DNS Server Service Overview of Domain Name System What Is a Domain Namespace? Standards for DNS Naming.
1 Domain Name System (DNS). 2 3 How DNS Works Application Transport Internet Network Application Transport Internet Network DNS Resolver Name Server.
1 Internet Network Services. 2 Module - Internet Network Services ♦ Overview This module focuses on configuring and customizing the servers on the network.
TCP/IP Protocol Suite 1 Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Chapter 19 Domain Name System (DNS)
Linux Operations and Administration
McGraw-Hill©The McGraw-Hill Companies, Inc., 2000 Chapter 18 Domain Name System (DNS)
AfNOG-2003 Domain Name System (DNS) Ayitey Bulley
Web Server Administration Chapter 4 Name Resolution.
1 CMPT 471 Networking II DNS © Janice Regan,
TCP/IP Protocol Suite 1 Chapter 17 Upon completion you will be able to: Domain Name System: DNS Understand how the DNS is organized Know the domains in.
COMP 431 Internet Services & Protocols
Internet Naming Service: DNS* Chapter 5. The Name Space The name space is the structure of the DNS database –An inverted tree with the root node at the.
Domain Name System DPNM Lab. Seongho Cho
Domain Name System: DNS To identify an entity, TCP/IP protocols use the IP address, which uniquely identifies the Connection of a host to the Internet.
1 Internet Service DNS & BIND OPS335 Seneca College of Applied Technology.
DNS and Inbound Load Balancing
DNS Domain name server a server to translate IP aliases to addresses
Domain Name System (DNS)
Domain Name System (DNS)
Networking Applications
Domain Name System: DNS
Chapter 9: Domain Name Servers
Module 5: Resolving Host Names by Using Domain Name System (DNS)
IMPLEMENTING NAME RESOLUTION USING DNS
Configuring and Troubleshooting DNS
Chapter 25 Domain Name System.
LINUX ADMINISTRATION 1
DNS.
Domain Name System (DNS)
Name Resolution in Windows Server 2012 (R2)
CpSc 360: Distributed and Network Programming
Net 323 D: Networks Protocols
Chapter 19 Domain Name System (DNS)
Domain Name System (DNS)
Chapter 25 Domain Name System
Chapter 25 Domain Name System.
Domain Name System Refs: Chapter 9 RFC 1034 RFC 1035.
Chapter 25 Domain Name System
Domain Name System: DNS
The Domain Name System.
Presentation transcript:

DNS : Domain Name System Surasak Sanguanpong nguan@ku.ac.th http://www.cpe.ku.ac.th/~nguan Last updated: May 24, 1999

Outline DNS basic name space name resolution process protocol configurations

Why need DNS? host table /etc/hosts compiled from HOST.TXT (maintain by SRI NIC) simple text file with has IP address to name mapping problems traffic and load name collision consistency A hierarchical name with distributed control is needed

DNS basic DNS is a distributed database TCP/IP applications use DNS to map hostname to IP address map IP address to hostname provide e-mail routing information mail nguan@cpe.ku.ac.th => mail.cpe.ku.ac.th handle aliases www.eng.ku.ac.th is actually is1.eng.ku.ac.th

Naming Scheme cc.cpe.ku.ac.th name space is a tree of domain building tree from top to bottom th more specific ac ku name space is a tree of domain names are case-insensitive cpe cc cc.cpe.ku.ac.th

Domain Name Space root ac usu in-addr ku tu cc cpe eng cc arpa com edu gov int mil net org au th ac usu in-addr ku tu cc cc.usu.edu cpe eng cc cc.cpe.ku.ac.th generic domains country domains arpa domains

DNS Management NIC manages root and top level domain name managed by NIC root managed by Internic Thailand th com NIC manages root and top level domain name local admins manage 3rd level or more ac or ku tu cpe eng manage by tu managed by ku

Domain Name Concept label every node has a label (except root) th domain name the list of labels, starting at that node, working up to the root, using a “.” to separate ac e.g. ku.ac.th, cpe.ku.ac.th ku absolute domain name domain name that ends with a period e.g. cc.cpe.ku.ac.th. cpe relative domain name name to be completed cc e.g. cc

Domains domain subtree of the domain name space th ac ku tu cpe eng cc ac.th domain ac ku tu ku.ac.th domain cpe eng cc cc.cpe.ku.ac.th node

Domains and Zones Zone is a subtree for which naming authority has been delegated ku.ac.th domain ku.ac.th domain ku.ac.th zone ku.ac.th zone ku ku ee ee sci sci eng eng rdi rdi lib kps kps lib cpe cpe case 1 : single DNS administration case 2 : cpe and eng have authority for their zones

Name Servers Name server : Server that store information about the zone ns.eng.ku.ac.th ns.ku.ac.th responsibility for eng.ku.ac.th zone ku ee responsibility for ku.ac.th zone sci eng rdi lib ns.cpe.ku.ac.th kps cpe responsibility for cpe.ku.ac.th zone

Type of Name Servers Primary Name server gets the data for zones from files on the host it runs on Secondary Name server gets its zone data from the primary for redundancy and workload distribution ns.eng.ku.ac.th : primary ns.ku.ac.th : primary ns2.eng.ku.ac.th : secondary nontri.ku.ac.th: secondary ku ee sci ns.cpe.ku.ac.th: primary eng rdi lib kps cpe cc.cpe.ku.ac.th: secondary

Zone Transfer Secondary Name Server pulls zone data over from the primary called zone transfer. ns.eng.ku.ac.th ns.ku.ac.th primary for eng.ku.ac.th secondary for ku.ac.th secondary for cpe.ku.ac.th primary for ku.ac.th secondary for cpe.ku.ac.th ns2.eng.ku.ac.th secondary for eng.ku.ac.th nontri.ku.ac.th secondary for ku.ac.th secondary for cpe.ku.ac.th ns.cpe.ku.ac.th primary for cpe.ku.ac.th secondary for ku.ac.th secondary for eng.ku.ac.th cc.cpe.ku.ac.th secondary for cpe.ku.ac.th

when I don’t have more info Root Name Server name server must contact other name servers for non local IP it has to know IP address of the top most server called root name server root name server - provide the names and address of the name server authoritative for top level domain name I have to connect root, when I don’t have more info root ns.ku.ac.th

Root Name Server (cont.) 13 root servers are currently available in Internet (Last updated Aug 97) A.ROOT-SERVERS.NET 198.41.0.4 B.ROOT-SERVERS.NET 128.9.0.107 C.ROOT-SERVERS.NET 192.33.4.12 D.ROOT-SERVERS.NET 128.8.10.90 E.ROOT-SERVERS.NET 192.203.230.10 F.ROOT-SERVERS.NET 192.5.5.241 G.ROOT-SERVERS.NET 192.112.36.4 H.ROOT-SERVERS.NET 128.63.2.53 I.ROOT-SERVERS.NET 192.36.148.17 J.ROOT-SERVERS.NET 198.41.0.10 K.ROOT-SERVERS.NET 193.0.14.129 L.ROOT-SERVERS.NET 198.32.64.12 M.ROOT-SERVERS.NET 202.12.27.33 ftp://ftp.rs.internic.net/domain/named.root

Name Resolution Process address of www.ku.ac.th? name server root name server ask th name servers address of www.ku.ac.th? th th name server ask ac.th name servers address of www.ku.ac.th? ac.th name server ac or ask ku.ac.th name server address of www.ku.ac.th? ku.ac.th name server ku tu ask ns.ku.ac.th name server address of www.ku.ac.th? ns.ku.ac.th name server www address is 158.108.2.69 address is 158.108.2.69 resolver address of www.ku.ac.th?

Reverse Resolution root au th arpa in-addr.arpa domain in reverse direction of IP address ac in-addr ku tu 255 158 255 cpe eng 108 255 34 cc 255 cc.cpe.ku.ac.th 3 3.34.108.158.in-addr.arpa

Caching all name servers employ a cache to reduce the DNS traffic standard UNIX keep cache in name server with time-out cache data is non-authoritative

1 or more additional information DNS message format (I) 0 15 16 31 identification:16 flags:16 number of questions :16 number of answer RRs:16 number of authority RRs :16 number of additional RRs:16 1 or more questions 1 or more answers 1 or more authority 1 or more additional information = fixed header query reply fixed 12 byte header with 4 variable length fields DNS message format is defined for both queries and answers

DNS message format (II) 0 15 16 31 identification:16 flags:16 set by the client and return by the server lets the client match responses to requests

DNS message format (III) identification:16 flags:16 QR opcode AA TC RD RA (zero) rcode 1 4 1 1 1 1 3 4 QR 0= query, 1= response opcode 0= standard query, 1=inverse query, 2=server status request AA 0= authoritatived answer,1 = non authoritatived answer TC 1= truncated. using UDP, reply was>512 bytes, return only 512 bytes RD 1= recursive desired, 0= iterative RA 1= recursion available (server support recursion) rcode return code : 0=no error, 3=name error

DNS message format (IV) questions :32 query name query type query class query class normally =1 means Internet Address 3www3cpe2ku2ac2th0 query name is the name being lookup, sequence of label begins with 1-byte count NS 2 name server PTR 12 pointer record MX 15 mail exchange record A 1 IP address CNAME 5 canonical name HINFO 13 host info query type indicates desired response

1 or more additional information DNS message format (V) 1 or more answers 1 or more authority 1 or more additional information = reply domain name type class time-to-live resource data resource length = = these three fields share a common resource record (RR) = domain name : corresp. response name, (query name format) type : response RR type code (see query type) time-to-live : cache life time of RR (often 86400=1 day) resource length : specify the size of resource data resource data : the answer, e.g. IP address or other type

Operations use port 53 typically UDP request and reply if answer is too big, use TCP ip hdr UDP hdr DNS hdr query answer#1 answer#2

Resolver file resolver must have address for local name server /etc/resolv.conf on UNIX /etc/resolv.conf # domain domain cpe.ku.ac.th # list of name server nameserver 158.108.32.5 nameserver 158.108.33.3 nameserver 158.108.2.67

Setting up DNS BIND (Berkeley Internet Name Domain) package /usr/somewhere/in.named - BSD named DNS server /etc/named.boot - named configuration (tell named where to find database files)

Sample named.boot ; Boot file for server ns.cpe.ku.ac.th. directory /usr/local/named cache . root.cache primary localhost. primary/local primary 0.0.127.in-addr.arpa primary/local.rev primary cpe.ku.ac.th primary/cpe secondary ku.ac.th 158.108.2.67 secondary/ku secondary cpc.ku.ac.th 158.108.2.67 secondary/cpc secondary eng.ku.ac.th 158.108.40.196 secondary/eng secondary 108.158.in-addr.arpa 158.108.2.67 secondary/ku.rev primary 32.108.158.in-addr.arpa primary/zone/zone32 primary 33.108.158.in-addr.arpa primary/zone/zone33 : : :

New named.conf format BIND Version 8 defines a new format of boot file : named.conf options { directory "/usr/local/named"; }; zone "." { type hint; file "root.cache"; zone "localhost." { type master; file "primary/local"; zone "0.0.127.in-addr.arpa" { type master; file "primary/local.rev"; }; zone "cpe.ku.ac.th" { file "primary/cpe"; zone "ku.ac.th" { type slave; masters { 158.108.2.67; :

Sample database file ; address file for server ns.cpe.ku.ac.th. (primary/cpe) @ IN SOA ns.cpe.ku.ac.th. dnsadmin.ns.cpe.ku.ac.th. ( 1998051300 ; Last Updated May 13,1998 10800 ; Refresh every 3 hours 3600 ; Retry every 1 hour 2592000 ; Expire after 30 days 86400 ; Minimum TTL of 1 day ) ; Name Servers IN NS ns.cpe.ku.ac.th. IN NS ns.eng.ku.ac.th. IN NS ns.ku.ac.th. (continue on next page)

Sample database file (cont.) ; Mail Hubs for the Domain IN MX 10 mailhost.cpe.ku.ac.th. IN MX 15 cc.cpe.ku.ac.th. ; AI Lab mars IN HINFO "MP 1101D/DECstation 5000-420" IN MX 10 mailhost.cpe.ku.ac.th. IN A 158.108.32.97 maspar IN CNAME mars.cpe.ku.ac.th. saturn IN HINFO "SPARCstation 2" "SunOS 4.1.3" IN MX 10 mailhost.cpe.ku.ac.th. IN A 158.108.32.98 ailab2 IN CNAME saturn.cpe.ku.ac.th.