PROJECT ON

REPRESENTED BY PATEL HIMANSHU N (AL013010) UNDER GIUDI BY URVASHI MAM

This is to certify that Mr. PATEL HIMANSHU N, roll no. is AL013010 and batch no. AL01210, the student of Jetking institute has successfully completed his assignment in module 3.
SIGNATURE OF SIGNATURE OF FACULTY EXAMINER

SIGNATURE WITH STAMP (HEAD OF DEPARTMENT)

INDEX INTRODUCTION DNS Name Resolution Process FEATURES DNS COMPONENTS DNS QUERY DNS CONCERNS ACKNOWLEDGEMEN

INTRODUCTION
The Domain Name System (DNS) is a hierarchical naming system for computers, services, or any resource connected to the Internet or a private network. It associates various information with domain names assigned to each of the participants. Most importantly, it translates domain names meaningful to humans into the numerical (binary) identifiers associated with networking equipment for the purpose of locating and addressing these devices worldwide. An often-used analogy to explain the Domain Name System is that it serves as the "phone book" for the Internet by translating human-friendly computer hostnames into IP addresses. For example, www.example.com translates to 192.0.32.10. The Domain Name System makes it possible to assign domain names to groups of Internet users in a meaningful way, independent of each user's physical location. Because of this, World Wide Web (WWW) hyperlinks and Internet contact information can remain consistent and constant even if the current Internet routing arrangements change or the participant uses a mobile device. Internet domain names are easier to remember than IP addresses such as 208.77.188.166 (IPv4) or 2001:db8:1f70::999:de8:7648:6e8 (IPv6). People take advantage of this when they recite meaningful URLs and e-mail addresses without having to know how the machine will actually locate them. Prior to the introduction of DNS in 1983 , the computers on network retrieved the host.txt file from the network information center. The host.txt file is used to provide the name of the domains mapped to their ip addresses.

DNS Name Resolution Process

FEATURE
I. DNS is a Database:
Keys to the database are domain names www.foo.com, 18.in-addr.arpa, 6.4.e164.arpa

Over 100,000,000 domain names are now stored. Each domain name contains one or more attributes, known as resource records. Each attribute is individually retrievable.

I. Global Distribution:
Data is maintained locally, but retrievable globally No single computer has all DNS data DNS lookups can be performed by any Internet-connected device Remote DNS data is locally cacheable to improve performance

I. 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 change Changes to the master copy of the database are replicated according to timing set by the zone administrator

Cached data expires according to timeout set by zone administrator.

I.

Scalability:
No intrinsic limit to the size of the database Some servers have over 20,000,000 names Not a particularly good idea No limit to the number of queries 80,000 queries per second handled regularly Queries distributed among many different servers

I.

Reliability:

Data is replicated Data from master source is copied to multiple slave servers Clients can query master server or slave servers DNS protocols can use either UDP or TCP UDP is inherently unreliable, but the DNS protocol handles retransmission (perhaps with TCP), sequencing, et cetera.

I.

Dynamic Updates:

Database can be updated dynamically Master server accepts update from over the network

 Add/delete/modify any record Modification of the master database triggers replication Only master can be dynamically updated Dynamic updates create a single point of failure

DNS COMPONENTS
DNS server :- Manage the DNS database that they host. The computer,
on which the DNS server service runs, is known as DNS server. The DNS server can be primary , secondary , or caching-only. In short , a DNS server is a computer that runs a DNS server program . The DNS server can be authoritative for either one or more levels of domain hierarchy.

Represent a certain portion within the global DNS. The DNS zone represents a boundary of authority that is subject to management by certain entities. It consists of the name and ip address information about one or more parts of a DNS domain. The file that contains the data of the zone for which a server is authoritative is called zone files.

DNS zone :-

Use the DNS protocol to query any information from the DNS server. It is a service that queries for the by communicating with either the DNS server or the DNS server program running on the local computer. The DNS client service also perform the function of caching the DNS mappings.

DNS resolvers :-

Answer for the DNS client queries. They are used to answer queries for the associated DNS namespace.

Resource record :-

DNS QUERY
A DNS query is used when a DNS client need to search a name that is used by an application. A DNS query consists Of the following three pieces of information.

The DNS domain name , know an FQDN. The query which specifies either a resource record by type or some special type of query operation. The specified class for the DNS domain name.

Iterative query Returns the best answer of the query that a client asks
the DNS sever. If the server does not have an answer the query may direct the client to another server through referral.

Recursive query Returns the requested answer or an error message of

the query that the client sends to the server.

Inverse query use the IP address and then asks for the name in the
query.

DNS CONCERNS
I)

Load Concerns:

DNS can handle the load DNS root servers get approximately 3000 queries per second Empirical proofs (DDoS attacks) show root name servers can handle 50,000 queries per second Limitation is network bandwidth, not the DNS protocol in-addr.arpa zone, which translates numbers to names, gets about 2000 queries per second

I)

Performance Concerns:

DNS is a very lightweight protocol Simple query response Any performance limitations are the result of network limitations

 Speed of light Network congestion Switching/forwarding latencies

ACKNOWLEDGEMENT
THE DISSERTATION WAS UNDERTAKEN IN PART FULFILLMENT OF THE REQUIREMENT FOR THE JCHNP OF JETKING HARDWARE AND NETWORKING INSTITUTE. I UNDERTAKE THIS OPPORTUNITY TO EXPRESS MY VIEWS AND INCREASE GRATITUDE OF MINE BY THE GUIDE FROM URVASHI MAM . FOR THE HELP & ADVICE THAT GIVEN BY TIME TO TIME.

BIBLIOGRAPHY
I AM VERY MUCH THANKFUL TO MRs, URVASHI MAM WHO HELPD ME IN DOING THIS PROJECT. HE ALSO HELP TO SOLVE MY PROBLEMS WHICH I HAVE FACED WHILE DOING THESE PROJECT. I ALSO WANT TO THANK JETKING INSTITUTE FOR THIS GREAT OPPORTUNITY.