DNS (Domain Name Systems)

Updated 29 October 2025

Introduction

The online available website hosts on a server which is connected to the internet through the Public IP Address. That IP address is very hard for a normal human being to remember.

To solve this problem, we developed the technique to use an alias on which the IP Address of the website should be matched.

For example, “www.google.com” can be mapped on the IP Address and it is very easy for us to remember this.

One more reason is that the IP Address can be changed at anytime and it would be a nightmare to keep track of all the websites you visit. The DNS translates the IP address on its own and thus you don’t have to remember the IP addresses.

Lets work on an example.

Type the following in your terminal:

bash
dig google.com

You will get the following result:

Image from notes

Now if you type the IP address 172.217.26.78 in your browser then you will see that it will open the page of Google. It is to keep in mind that when you run this then there is a possibility that this IP address gets changed. Now here comes the DNS to our rescue.

Before diving further into the DNS, lets find out about it.

Anatomy

We can define the anatomy of DNS as the following

Image from notes

FQDN (Fully Qualified Domain Name) facilitates accurate resource identification. In essence, they provide a clear pathway for navigating the Internet’s distributed network. Using Fully Qualified Domain Name ensures precise communication and resource retrieval, contributing to the overall efficiency and reliability of online interactions.

  • Root
  • Top level
  • Second Level Domain
  • Sub Domain

We can take the following example:

Image from notes

In this example, we have used “engineer.kodekloud.com” as the address and we can break it down as follows:

Root Zone: .

Top Level Domain: com

Second Level Domain: kodekloud

Sub Domain: engineer

Spotted a mistake or want something added? Send me a note.