chapter
    Application Layer Protocols and Web Communication Notes for GATE CS

    Application Layer Protocols and Web Communication notes for GATE CS: 29 study cards covering concepts, formulas, shortcuts and exam traps, plus solved practic

    application layer protocols and web communication notes

    Chapter Roadmap: Application Layer Protocols and Web Communication

    Chapter Roadmap: Application Layer Protocols and Web Communication

    1. DNS Resolution and Web Request Sequencing
    Focus: High. Foundation for all web latency problems. Master the exact packet order and iterative query counting.
    2. HTTP Connections, Persistence and Web Latency
    Focus: High. Master RTT calculations for non-persistent versus persistent HTTP with and without pipelining.
    3. Application Protocol Message Delivery
    Focus: Moderate. Understand port numbers, UDP versus TCP usage in application protocols, and broadcast requirements.

    Topic Hero: DNS Resolution and Web Request Sequencing

    Topic Hero: DNS Resolution and Web Request Sequencing

    The Bridge from Human Name to Data Transfer

    Before any web content can be fetched, the system must complete a strict sequence of network events. This topic focuses on:

    • Name Resolution: Translating a human-readable domain name into an IP address.
    • Connection Establishment: The three-way TCP handshake to create a reliable pipe.
    • Application Request: The first HTTP GET message sent over that established pipe.

    Understanding this exact sequence is the prerequisite for calculating total web page fetch time and identifying correct packet traces.

    The Three-Tier DNS Hierarchy

    The Three-Tier DNS Hierarchy

    The Domain Name System (DNS) is a distributed database organized in a strict hierarchy. When a cache is empty, resolution flows through three distinct tiers:

    Tier Server Type Responsibility
    1 Root DNS Server Knows the IP addresses of all Top-Level Domain (TLD) servers.
    2 TLD Server Manages a specific domain extension (e.g., .com, .org, .in). Knows the authoritative servers for domains within that extension.
    3 Authoritative DNS Server The final source of truth. Holds the actual resource records (like the A record mapping a name to an IPv4 address) for its specific domain.
    Note: The user's computer first contacts a Local DNS Server (often provided by the ISP), which acts as a proxy to traverse this hierarchy.

    26 more cards in this chapter

    Free preview ends here

    Login to view the complete notes

    Creating an account is free. You get the rest of this chapter, step-by-step solutions, and a study plan built around the topics you are actually weak at.

    Login to continueSee plans
    Why MastersUp

    Personalised first. High quality throughout.

    Most platforms hand everyone the same content. Here the content moves with your performance, topic by topic.

    Built around you, not around a syllabus PDF

    Every answer you give moves your topic-level intelligence rate. The next question, the next revision card and tomorrow's plan all change with it.

    Revision that hits your weak spots

    We only revise topics you have actually attempted and are still below the safe bar on — never the same chapter on repeat.

    Questions calibrated to the real exam

    Each question carries a measured toughness. You are served a rung above your current level, so practice keeps stretching you.

    Notes written for recall, not for volume

    Full lesson cards for first study, curated short-note cards for the last mile — with derivations, traps and exam patterns marked.

    One place for everything

    Notes, chapter practice, previous-year questions, test series and full-length papers — all feeding one picture of your preparation.

    Honest progress

    No vanity streaks. Progress here means chapters mastered and accuracy that held up on harder questions.

    Unlock the whole course

    Full notes and short notes, the complete question bank with worked solutions, mock tests, full-length papers, and an adaptive plan that rebuilds itself as you improve.

    View all plansStart free

    Application Layer Protocols and Web Communication Notes for GATE CS

    Application Layer Protocols and Web Communication notes for GATE CS: 29 study cards covering concepts, formulas, shortcuts and exam traps, plus solved practice questions.

    Chapter Roadmap: Application Layer Protocols and Web Communication

    Chapter Roadmap: Application Layer Protocols and Web Communication

    1. DNS Resolution and Web Request Sequencing
    Focus: High. Foundation for all web latency problems. Master the exact packet order and iterative query counting.
    2. HTTP Connections, Persistence and Web Latency
    Focus: High. Master RTT calculations for non-persistent versus persistent HTTP with and without pipelining.
    3. Application Protocol Message Delivery
    Focus: Moderate. Understand port numbers, UDP versus TCP usage in application protocols, and broadcast requirements.

    Topic Hero: DNS Resolution and Web Request Sequencing

    Topic Hero: DNS Resolution and Web Request Sequencing

    The Bridge from Human Name to Data Transfer

    Before any web content can be fetched, the system must complete a strict sequence of network events. This topic focuses on:

    • Name Resolution: Translating a human-readable domain name into an IP address.
    • Connection Establishment: The three-way TCP handshake to create a reliable pipe.
    • Application Request: The first HTTP GET message sent over that established pipe.

    Understanding this exact sequence is the prerequisite for calculating total web page fetch time and identifying correct packet traces.

    The Three-Tier DNS Hierarchy

    The Three-Tier DNS Hierarchy

    The Domain Name System (DNS) is a distributed database organized in a strict hierarchy. When a cache is empty, resolution flows through three distinct tiers:

    Tier Server Type Responsibility
    1 Root DNS Server Knows the IP addresses of all Top-Level Domain (TLD) servers.
    2 TLD Server Manages a specific domain extension (e.g., .com, .org, .in). Knows the authoritative servers for domains within that extension.
    3 Authoritative DNS Server The final source of truth. Holds the actual resource records (like the A record mapping a name to an IPv4 address) for its specific domain.
    Note: The user's computer first contacts a Local DNS Server (often provided by the ISP), which acts as a proxy to traverse this hierarchy.

    Iterative vs Recursive DNS Resolution

    Iterative vs Recursive DNS Resolution

    The behaviour of the DNS resolver changes the number of messages and the load on servers.

    Iterative Query (Standard)

    The requesting server (Local DNS) does the legwork.

    1. Local DNS asks Root. Root replies: "I do not know, but here is the TLD server's address."
    2. Local DNS asks TLD. TLD replies: "I do not know, but here is the Authoritative server's address."
    3. Local DNS asks Authoritative. Authoritative replies with the final IP address.
    Recursive Query (Rare)

    The receiving server does the legwork.

    1. Local DNS asks Root and demands a final answer.
    2. Root server itself queries the TLD, then the Authoritative server.
    3. Root returns the complete IP address back to the Local DNS.
    Exam Rule: Default to iterative resolution for the public DNS hierarchy unless the problem explicitly specifies recursive behaviour.

    More notes in this unit