Let's look at a domain name such as icann.org. This is essentially the address of any entity on the Internet. It can be a person or an organization on the Internet. The domain name is a mapping of this IP address, of a public computer on the Internet to a pneumonic address that can be more easily remembered or the domain name.

The domain name has three parts.
The first is the subdomain labeled such as the www, which is like worldwide web or mail, M-A-I-L.
These subdomains are managed by the host of the domain and can be used to organize services offered by that host. For instance www for world wide web. And the domain labels such as ICANN in www.icann.org, it must be unique within the top level domain.
And the fullest of them can be available on the Internet. Anyway, it has different extensions such as .science, .iu, .dentist. And when you type an Internet address in your browser your computer makes a request to a domain name server. Now DNS servers are typically operated by your own organization or Internet service provider. Then again, local directories of the gateways. For example, if a university will operate a domain name server to manage all the internal IP addresses to easy to remember pneumonic names.
This internal domain name service can also look up Internet addresses for services that are outside of your internal network.
The domain name server, much like a phone book, it's really like a phone book. It will compare the name to a list of numbers. When it locates a match, it responds to your computer with the number for your service.
As new domain names are registered or existing computers change, the addresses, the relationship between names and numbers, they need to be constantly updated, and that happens.
Symantec Corp.

This redundancy is really required in case one of the servers is unreachable or fails. In addition, we have two different types of name servers, a master and a slave. The master server maintains the original copies of the domain name records in the zone. And the zone can be anything from a geographic region to a specific organization to a top level domain. And what the slave does is it basically automatically syncs in with the master. And the slave is what is the public facing end of the domain name server.

And so as we reject this bad host we're basically able to cause some filtration. Now, there's one important difference between a phone book and a domain name system that does not exist in the phone book. One is the phone book is a one to one mapping between the numbers and names, and the domain servers have multiple mapping. A single Internet address can correspond to multiple domain names, and multiple domain names can point to a single IP address. And multiple IP addresses can point to a single domain name. The reason for that is flexibility and scalability. If the same server is going to serve multiple domains or multiple functions and use, that's why we have multiple domain mains go to the same IP address. And to provide scalability to very large organization like Google, they can have the same domain name like google.com assigning itself to multiple IP addresses for scalability.

And so that allows them to provide a fast response to any of the requests that were made in real time and that's why it is important to make sure that multiple IP addresses can be allocated to the same domain. For instance, Google had their servers scattered throughout the globe and based where the request comes from it can go to the specific IP address within the local region.
Who manages Domain Name System?
1. your organization
2. ISP The Teacher Store
Cyber conflicts in the Domain Name System (DNS) involve attacks such as DNS spoofing, hijacking, and DDoS DomaiNesia, which disrupt internet communication by manipulating domain name resolution processes.
ReplyDelete