Video summary

DNS Malayalam - Domain Name System for Beginners

Main summary

Key takeaways

Educational

Main ideas / lessons

  • Humans identify people by names, but networks identify devices/services by numbers.
  • In networking, devices and services are identified using IP addresses:
    • An IP address is described here as a 32-bit number.
    • Websites/servers (e.g., Google, Gmail, Amazon) therefore have:
      • an IP address
      • and a port number
  • Without DNS, you would have to access websites by typing the IP address + port for each site.
  • DNS (Domain Name System) solves this problem by mapping readable domain names to IP addresses, so users can type something like amazon.com instead of an IP address.
  • The core DNS concept described:
    • Domain name → IP address mapping is called DNS resolution.
  • DNS resolution is performed by systems outside the browser, involving:
    • the local computer,
    • an ISP (resolver),
    • and multiple layers of DNS servers (root → TLD → authoritative).

DNS resolution flow (step-by-step)

When a user types a domain name in a browser (example: yahoo.com), the process is:

  1. Step 1: Browser/computer checks locally

    • Check the computer’s cache memory for the domain name.
    • Check the computer’s hosts file:
      • If the hosts file contains a manual mapping (domain → IP), it’s used.

  2. Step 2: Ask the DNS resolver (typically ISP)

    • If no mapping is found locally, the request goes to a domain name resolver, typically the ISP’s resolver.
    • If the ISP resolver can’t resolve the name, it proceeds to the next DNS layer.

  3. Step 3: Root DNS server

    • The ISP resolver sends the request to a root DNS server.
    • Root servers do not provide the final IP for domains like yahoo.com.
    • Instead, the root server replies with information about which TLD (top-level domain) server to contact.
    • The video states:
      • There are 13 root DNS servers worldwide.
      • They are managed by 12 organizations (as stated).
      • Each root server has its own IP address.

  4. Step 4: TLD (Top-Level Domain) server

    • The resolver queries the TLD server responsible for the domain’s TLD:
      • Example: .com is a top-level domain.
    • The TLD server may also not have the final domain IP itself.
    • Instead, it points the resolver toward the authoritative name server responsible for that specific domain (e.g., the server for yahoo.com).

  5. Step 5: Authoritative name server (final answer)

    • The resolver asks the authoritative name server for yahoo.com.
    • This server returns the final IP address for the domain.

  6. Step 6: Return IP to the computer

    • The resolver sends the IP address back to the requesting computer.
    • The computer then uses that IP address to access the correct website/server.

  7. Step 7: Caching

    • After resolution, the resolver stores the domain → IP mapping in cache for some time.
    • Future requests for the same domain can be answered from cache, reducing the need for repeated lookups.

Speakers / sources featured

  • No specific human speaker name is provided in the subtitles (only implied narration).
  • Systems/components mentioned (not as people):
    • hosts file (on the user’s computer)
    • DNS resolver / ISP
    • root DNS servers
    • TLD servers
    • authoritative name servers
    • web browser (as the initiating client)

Original video