The Domain Name System (DNS) handles the growing number of Internet users. Cisco Prime Network Registrar Caching and Authoritative DNS User. Tutorial Focus: Big picture. - Not software help. - DNS!= BIND. - No gory protocol Domain name: any name represented in the DNS format. And in the case of DNS, practically all Internet hosts participate directly in the DNS as a client, server or both. .. DNS Tutorial @ IETF 80 – Gudmundsson, Koch.
|Language:||English, Spanish, German|
|ePub File Size:||30.41 MB|
|PDF File Size:||9.51 MB|
|Distribution:||Free* [*Sign up for free]|
Americans use the Internet. While that might sound pretty average, let's compare that to the whole planet where only 4 in 10 people use the Internet. With all this. and has a built in table of name to address translation u Problem: Not scalable u Solution: DNS (Adopted in ) u Hierarchical Names: portal7.info-state. In this tutorial I will explain the basics of DNS starting with the hosts file, and explain how and why DNS evolved,, and the problems DNS was.
Understanding how DNS works will help you diagnose problems with configuring access to your websites and will allow you to broaden your understanding of what's going on behind the scenes. In this guide, we will discuss some fundamental DNS concepts that will help you hit the ground running with your DNS configuration. After tackling this guide, you should be ready to set up your domain name with DigitalOcean or set up your very own DNS server. Before we jump into setting up your own servers to resolve your domain or setting up our domains in the control panel, let's go over some basic concepts about how all of this actually works. Domain Terminology We should start by defining our terms. While some of these topics are familiar from other contexts, there are many terms used when talking about domain names and DNS that aren't used too often in other areas of computing.
The DNS system provides a domain name to IP address mapping for devices connected to the Internet, and it is crucial to the working of the Internet.
Thank you good material. Now I need to be able to configure my Windows dns server which we need? How can I locate where a persons email that I receive is located in what country?. I want to avoid fraudulent conversation.
Thank you. You need the IP address to locate the origin of the email. I tried to edit the host file to set the entry for http: I set the IP address for Microsoft to google and it opened the site any reason for this? Your email address will not be published.
Leave this field empty. DNS Basics — Understanding Why we Need it All devices computers etc that are connected to the Internet, your own network, or company network are identified by an IP address; which is a number.
IP addresses are easy for computers to process but they are not so easy for people to remember.
Here is the host file taken from my PC. It needed to be stored on each computer The text file could take a along time to process due to the fact that it was unstructured. Updates were difficult to manage as all of the computers would need to be given an updated file.
To overcome these and other limitations the DNS system was developed. The DNS system essentially provides for: A way to organize the names- Domain name structure Protocols ,services and methods for storing,updating, and retrieving IP addresses for hosts computers. Domain Name Structure The hosts file is simply a list of names and IP addresses with no structure making it difficult to scale to a large number of machines.
However you need to have access to a DNS server. Most security internet product suites will use some form of filtered DNS. DNS server addresses are: IP addresses are: Terms like zones, zone files, caching server etc. This video is a good introduction to understanding those basic terms.
Summary The DNS system provides a domain name to IP address mapping for devices connected to the Internet, and it is crucial to the working of the Internet. Thanks Mr. For instance, the "com" TLD has both "google. A "subdomain" refers to any domain that is part of a larger domain.
In this case, "ubuntu. This is typically just called the domain or the "ubuntu" portion is called a SLD, which means second level domain. Likewise, each domain can control "subdomains" that are located under it. This is usually what we mean by subdomains. For instance you could have a subdomain for the history department of your school at " www. The "history" portion is a subdomain. The difference between a host name and a subdomain is that a host defines a computer or resource, while a subdomain extends the parent domain.
It is a method of subdividing the domain itself. Whether talking about subdomains or hosts, you can begin to see that the left-most portions of a domain are the most specific.
This is how DNS works: from most to least specific as you read from left-to-right. Domains in the DNS system can be given relative to one another, and as such, can be somewhat ambiguous.
A FQDN is an absolute name that specifies its location in relation to the absolute root of the domain name system. This means that it specifies each parent domain including the TLD. An example of a FQDN is "mail. Name Server A name server is a computer designated to translate domain names into IP addresses.
These servers do most of the work in the DNS system. Since the total number of domain translations is too much for any one server, each server may redirect request to other name servers or delegate responsibility for a subset of subdomains they are responsible for.
Name servers can be "authoritative", meaning that they give answers to queries about domains under their control. Otherwise, they may point to other servers, or serve cached copies of other name servers' data.
Zone File A zone file is a simple text file that contains the mappings between domain names and IP addresses. This is how the DNS system finally finds out which IP address should be contacted when a user requests a certain domain name. Zone files reside in name servers and generally define the resources available under a specific domain, or the place that one can go to get that information.
Records Within a zone file, records are kept. In its simplest form, a record is basically a single mapping between a resource and a name. These can map a domain name to an IP address, define the name servers for the domain, define the mail servers for the domain, etc.
The system is very simple at a high-level overview, but is very complex as you look at the details.
Overall though, it is a very reliable infrastructure that has been essential to the adoption of the internet as we know it today. At the top of this system is what are known as "root servers".
There are currently 13 root servers in operation. However, as there are an incredible number of names to resolve every minute, each of these servers is actually mirrored. The interesting thing about this set up is that each of the mirrors for a single root server share the same IP address. When requests are made for a certain root server, the request will be routed to the nearest mirror of that root server. What do these root servers do?
Root servers handle requests for information about Top-level domains. So if a request comes in for something a lower-level name server cannot resolve, a query is made to the root server for the domain.
The root servers won't actually know where the domain is hosted. They will, however, be able to direct the requester to the name servers that handle the specifically requested top-level domain. So if a request for " www.
It will check its zone files for a listing that matches " www. It will not find one. It will instead find a record for the "org" TLD and give the requesting entity the address of the name server responsible for "org" addresses. TLD Servers The requester then sends a new request to the IP address given to it by the root server that is responsible for the top-level domain of the request.
So, to continue our example, it would send a request to the name server responsible for knowing about "org" domains to see if it knows where " www.
Once again, the requester will look for " www. It will not find this record in its files. However, it will find a record listing the IP address of the name server responsible for "wikipedia. This is getting much closer to the answer we want. Domain-Level Name Servers At this point, the requester has the IP address of the name server that is responsible for knowing the actual IP address of the resource.
It sends a new request to the name server asking, once again, if it can resolve " www. The name server checks its zone files and it finds that it has a zone file associated with "wikipedia.
Inside of this file, there is a record for the "www" host. This record tells the IP address where this host is located. The name server returns the final answer to the requester. What is a Resolving Name Server? In the above scenario, we referred to a "requester". What is the requester in this situation? In almost all cases, the requester will be what we call a "resolving name server" A resolving name server is one configured to ask other servers questions.
It is basically an intermediary for a user which caches previous query results to improve speed and knows the addresses of the root servers to be able to "resolve" requests made for things it doesn't already know about. Basically, a user will usually have a few resolving name servers configured on their computer system. The resolving name servers are usually provided by an ISP or other organizations.
For instance Google provides resolving DNS servers that you can query. These can be either configured in your computer automatically or manually. When you type a URL in the address bar of your browser, your computer first looks to see if it can find out locally where the resource is located. It checks the "hosts" file on the computer and a few other locations. It then sends the request to the resolving name server and waits back to receive the IP address of the resource.
The resolving name server then checks its cache for the answer. If it doesn't find it, it goes through the steps outlined above. Resolving name servers basically compress the requesting process for the end user.
The clients simply have to know to ask the resolving name servers where a resource is located and be confident that they will investigate and return the final answer. Zone Files We mentioned in the above process the idea of "zone files" and "records". Zone files are the way that name servers store information about the domains they know about.
Every domain that a name server knows about is stored in a zone file. Most requests coming to the average name server are not something that the server will have zone files for.
If it is configured to handle recursive queries, like a resolving name server, it will find out the answer and return it. Otherwise, it will tell the requesting party where to look next.
The more zone files that a name server has, the more requests it will be able to answer authoritatively. It generally is used to configure just a single domain. It can contain a number of records which define where resources are for the domain in question. So if a zone file is used to configure the "example. This is either configured at the top of the zone file or it can be defined in the DNS server's configuration file that references the zone file.
Either way, this parameter describes what the zone is going to be authoritative for. It is basically a timer. A caching name server can use previously queried results to answer questions until the TTL value runs out. Record Types Within the zone file, we can have many different record types. We will go over some of the more common or mandatory types here. It is also one of the most complex to understand.
The start of authority record looks something like this: domain. IN SOA ns1. This specifies that the zone file is for the domain. Name servers can either be master or slaves, and if dynamic DNS is configured one server needs to be a "primary master", which goes here.