GateAI

GATE CSE DNS and HTTP PYQs

Standard yield10.1% of Computer Networks

In GATE CS, the 'DNS and HTTP' topic is tested predominantly through conceptual protocol interaction, chronological packet sequencing, connection lifecycle mech… Read the guide

Questions
18
Asked
since 2011
Total marks
20
Marks / paper
0.8

18 GATE CSE DNS and HTTP PYQs with solutions, from Computer Networks. Browse all GATE CSE PYQs.

Questions

Every official paper that asked this topic, newest first.

What GATE tests in DNS and HTTP

Concepts, patterns, formulas and traps distilled from past papers.

In GATE CS, the 'DNS and HTTP' topic is tested predominantly through conceptual protocol interaction, chronological packet sequencing, connection lifecycle mechanics, and timing calculations. Early exams focused on basic protocol roles (SMTP, POP3, HTTP), statefulness, and HTML/XML properties, whereas recent exams (2020–2026) strongly emphasize quantitative analysis of iterative DNS hierarchies, persistent vs. non-persistent HTTP, pipelining, and total round-trip time (RTT) latency.

Core concepts

  • DNS resolution mechanism (iterative vs. recursive, root, TLD, SLD, authoritative servers)
  • HTTP 1.0 non-persistent vs. HTTP 1.1 persistent connections
  • HTTP request pipelining and head-of-line considerations across a single TCP stream
  • Dependency ordering: DNS lookup -> TCP 3-way handshake (SYN) -> HTTP request -> HTTP response
  • Embedded web objects and parallel TCP connections
  • HTTP Cookies (text key-value pairs stored at client, Set-Cookie headers, expiration, statelessness mitigation)
  • Stateful vs. stateless protocols (HTTP is stateless; FTP and POP3 maintain state; TCP is stateful at transport layer)
  • Application-level email protocols (SMTP push vs. POP3/IMAP pull vs. HTTP webmail)
  • Dynamic Host Configuration Protocol (DHCP) bootstrapping and DORA process
  • Application-layer broadcasting mechanisms (e.g., DHCPDISCOVER using 255.255.255.255)
  • Unicast TCP-based protocols (HTTP, SMTP, FTP) vs. UDP/broadcast-capable protocols
  • Transport layer dependencies of application protocols (TCP vs. UDP)

Recurring question patterns

  • Chronological Sequence of Browser/Web Request Events

    CommonMCQ1 marks2024, 2016, 2014

    Determining the exact sequential order of protocol actions or packet transmissions when a client resolves an address, opens a transport connection, and requests web assets (DNS query -> TCP SYN/Handshake -> HTTP GET base page -> HTTP GET embedded resources).

  • Total RTT and Latency Calculation for Webpage Fetching

    Occasionalmixed2 marks2023, 2020

    Calculating the total elapsed time in multiples of RTT required to resolve domain names via iterative DNS servers, establish TCP connections, and fetch a base HTML document plus multiple embedded objects under varying modes (non-persistent parallel connections vs. persistent pipelined HTTP).

  • Iterative vs. Recursive DNS Query Hierarchy Counting

    OccasionalNAT1 marks2023, 2022

    Counting the exact number of query-response pairs or DNS server traversals needed to resolve a fully qualified domain name (FQDN) across root, TLD, and authoritative nameservers assuming cold caches.

  • HTTP Mechanics: Persistence, Pipelining, and Cookies

    Commonmixed1 marks2026, 2015, 2014

    Evaluating conceptual assertions regarding HTTP 1.0 vs. HTTP 1.1 features (persistent TCP connections, single vs multi-server socket constraints, pipelining) and session tracking via HTTP cookies.

  • Application Layer Protocol Characteristics and Role Mapping

    CommonMCQ1 marks2019, 2016, 2015, 2011

    Categorizing application-layer protocols based on statefulness (FTP, POP3 vs. stateless HTTP), address resolution nature (DNS, ARP, RARP vs. DHCP configuration), or specific application tasks (SMTP push vs. POP3/IMAP pull).

  • Protocol Transmission and Operational Behavior Identification

    RareMCQ1 marks2026

    Questions that present a specific communication characteristic (e.g., broadcasting messages, transport layer protocol dependency, statefulness) and ask the candidate to identify which application-layer protocol exhibits that behavior.

Formulas GATE uses

Non-Persistent HTTP Connection Count

TCP Connections=1+Nembedded objects\text{TCP Connections} = 1 + N_{\text{embedded objects}}

Used to compute total TCP handshakes when fetching a base HTML page containing NN embedded objects in non-persistent HTTP mode.

Iterative DNS Query-Response Pairs

Pairs=Lhierarchy=1 (Root)+∑intermediate domain levels+1 (Authoritative)\text{Pairs} = L_{\text{hierarchy}} = 1 \text{ (Root)} + \sum \text{intermediate domain levels} + 1 \text{ (Authoritative)}

Used when calculating the number of DNS query-response round trips needed without caching across an iterative DNS resolution tree.

Webpage Retrieval Delay (Non-persistent with $k$ parallel TCP connections)

Time=TimeDNS+2 RTTbase+2⌈Nk⌉RTT\text{Time} = \text{Time}_{\text{DNS}} + 2\text{ RTT}_{\text{base}} + 2 \left\lceil \frac{N}{k} \right\rceil \text{RTT}

Used to calculate elapsed RTTs when downloading base HTML followed by NN objects over at most kk concurrent non-persistent TCP connections.

Webpage Retrieval Delay (Persistent HTTP with Pipelining)

Time=TimeDNS+2 RTTbase+1 RTTpipelined objects\text{Time} = \text{Time}_{\text{DNS}} + 2\text{ RTT}_{\text{base}} + 1\text{ RTT}_{\text{pipelined objects}}

Used to calculate total RTTs when all embedded objects on the same server are requested in a single pipelined burst over the existing persistent connection.

Examiner traps in DNS and HTTP

  • Confusing transport-layer state with application-layer state: marking TCP as a stateful application layer protocol (GATE 2016 Set 1).
  • Believing cookies are executable security threats/code rather than static header data stored on the host (GATE 2015 Set 2).
  • Forgetting the initial 1 TCP connection / 2 RTTs required for the base HTML page before embedded objects can even be discovered and fetched (GATE 2020, 2023).
  • Assuming persistent HTTP 1.1 can multiplex requests across distinct physical servers in the same TCP connection (a TCP socket is strictly bound to one server IP:port) (GATE 2026 Set 1).
  • Counting only top-level domains and forgetting the root server or multi-level domains (e.g. counting '.org.in' as 1 instead of '.in' then 'org.in') in iterative DNS resolution (GATE 2022).
  • Mistaking DHCP for an address resolution protocol (it is host configuration/allocation, whereas DNS/ARP/RARP map identifiers) (GATE 2016 Set 1).
  • Assuming all application layer protocols operate strictly over point-to-point unicast TCP connections.
  • Overlooking that a host does not yet have an assigned IP address during initial DHCP discovery, mandating broadcast delivery.

How questions are asked

  • Chronological packet/event ordering
  • Multi-tier iterative DNS query counting (NAT)
  • Total RTT calculation with parallel/pipelined HTTP (MSQ/NAT)
  • Multi-statement correctness regarding HTTP versions, cookies, or persistent channels (MSQ)
  • Protocol classification and property matching
  • Direct protocol identification matching an operational property (e.g., message broadcast requirement)

Paper trends

  • Shift from qualitative protocol identification (SMTP, POP3, basic HTML tags) to rigorous multi-RTT latency calculations and deep HTTP 1.1 connection semantics.

    2026, 2023, 2020, 2014, 2011

  • Introduction of NAT and MSQ formats replacing simple 4-option MCQs to test multi-level iterative DNS resolution and combinatorial multi-statement evaluation.

    2026, 2023, 2022, 2020

  • Direct conceptual 1-mark MCQs focusing on fundamental communication needs (such as broadcast during bootstrap/discovery) among standard TCP/IP application layer protocols.

    2026

Difficulty notes

Easy: Single-concept protocol matching (SMTP/POP/HTTP), identification of stateless/stateful protocols, basic packet ordering, or simple non-persistent connection counting. Medium: Calculating multi-step RTT elapsed time under differing concurrency models (iterative DNS + parallel TCP vs. persistent pipelined HTTP), and rigorous evaluation of HTTP/1.1 socket boundaries and connection reuse (MSQ).