Application Layer Protocols: DNS, HTTP, FTP, DHCP – How the Web and Services Work

TAKEAWAYS:

• DNS translates human-readable domain names (e.g., www.esewa.com.np) into IP addresses using a hierarchical, distributed database of name servers.
• HTTP is a stateless, request-response protocol for fetching web pages (e.g., loading Daraz product pages), with versions HTTP/1.1 and HTTP/2 optimizing performance.
• FTP enables secure file transfers (e.g., uploading documents to a cloud server) using control and data connections, while SFTP/FTPS add encryption.
• DHCP automates IP address assignment in networks (e.g., Ncell’s Wi-Fi hotspots), reducing manual configuration via a four-step lease process (DORA).
• Each protocol operates at the application layer but relies on lower layers (e.g., TCP for reliability, UDP for speed) to deliver data.
• Security risks (e.g., DNS spoofing, HTTP man-in-the-middle attacks) require encryption (HTTPS, DNSSEC) and best practices like strong credentials.

1. Application Layer: The User-Facing Interface

The application layer (Layer 7 of the OSI model) is where users and applications interact with the network. Unlike lower layers (which handle data transmission), this layer defines protocols for specific services:

• DNS: Translates domain names to IPs.
• HTTP/HTTPS: Rules for web browsing.
• FTP/SFTP: File transfer protocols.
• DHCP: Automates IP address assignment.

These protocols are independent of hardware but depend on lower layers (e.g., TCP for reliability, UDP for speed). They use port numbers to identify services (e.g., port 80 for HTTP, 22 for SSH).

Why Protocols?

A protocol is a set of rules governing how data is formatted, transmitted, and interpreted between applications. For example:

• HTTP defines how a browser requests a webpage from a server.
• FTP specifies how files are uploaded/download in chunks.
• DNS dicts how name servers query each other.

The application layer sits atop the transport layer (TCP/UDP), which relies on the network layer (IP). (Image: SVG edition: Gorivero, CC BY-SA 3.0, via Wikimedia Commons)

2. Domain Name System (DNS): The Internet’s Phonebook

2.1 What is DNS?

DNS (Domain Name System) maps human-readable domain names (e.g., www.tribhuvan-university.edu.np) to IP addresses (e.g., 192.0.34.166). Without DNS, users would memorize IPs like 8.8.8.8 for Google’s DNS servers.

2.2 How DNS Works: A Step-by-Step Trace

When you type www.esewa.com.np in a browser, this happens:

1. Local Cache Check: Your device checks its local DNS cache (or browser cache).
2. Recursive Resolver Query: If not found, your ISP’s DNS resolver (e.g., NTC’s 203.120.144.10) queries the root name server (.).
3. Root → TLD → Authoritative Server:
   • Root refers to .np (top-level domain, TLD).
   • .np server refers to esewa.com.np’s authoritative server.
   • Authoritative server returns the IP (e.g., 103.12.160.10).
4. Response: The IP is cached locally and sent to your browser.

sequenceDiagram
    participant User
    participant LocalCache
    participant ISP_DNS
    participant Root
    participant NP_TLD
    participant ESEWA_AUTH
    User->>LocalCache: www.esewa.com.np?
    LocalCache-->>User: Not found
    User->>ISP_DNS: Query
    ISP_DNS->>Root: .np?
    Root-->>ISP_DNS: NP_TLD IP
    ISP_DNS->>NP_TLD: esewa.com.np?
    NP_TLD-->>ISP_DNS: ESEWA_AUTH IP
    ISP_DNS->>ESEWA_AUTH: IP?
    ESEWA_AUTH-->>ISP_DNS: 103.12.160.10
    ISP_DNS-->>User: IP + Cache

2.3 DNS Record Types

2.4 Why DNS? Real-World Example: eSewa Payments

When you pay a bill via eSewa’s website:

1. You type esewa.com.np.
2. DNS resolves this to 103.12.160.10.
3. Your browser connects to eSewa’s server via HTTP/HTTPS (port 443).
4. The server processes your payment request and returns a confirmation page.

Without DNS, you’d have to manually enter 103.12.160.10 every time—impossible for humans!

2.5 DNS Security Risks & Solutions

3. Hypertext Transfer Protocol (HTTP/HTTPS)

3.1 What is HTTP?

HTTP (Hypertext Transfer Protocol) is a stateless, text-based protocol for fetching web resources (HTML, images, videos). It runs on port 80 (HTTP) or 443 (HTTPS).

3.2 HTTP Request-Response Cycle

1. Client (Browser) sends a request (e.g., GET /index.html HTTP/1.1).
2. Server processes the request and sends a response (e.g., 200 OK with HTML).
3. Connection closes (unless Connection: keep-alive is used).

sequenceDiagram
    participant Browser
    participant Server
    Browser->>Server: GET /index.html HTTP/1.1 (Host: esewa.com.np)
    Server-->>Browser: HTTP/1.1 200 OK\nContent-Type: text/html
    Browser->>Server: GET /logo.png
    Server-->>Browser: HTTP/1.1 200 OK\nContent-Type: image/png

3.3 HTTP Methods

3.4 HTTP Status Codes

3.5 HTTP vs. HTTPS

Real-World Example: Daraz Shopping When you browse Daraz, HTTPS ensures:

• Your credit card details are encrypted.
• No third party can intercept your cart data.
• The website’s authenticity is verified via SSL certificates.

The green padlock in your browser confirms HTTPS. (Image: Sean MacEntee, CC BY 2.0, via Wikimedia Commons)

4. File Transfer Protocol (FTP)

4.1 What is FTP?

FTP (File Transfer Protocol) transfers files between a client and server using two connections:

1. Control Connection (port 21): Sends commands (e.g., USER, PASS, RETR).
2. Data Connection (port 20): Transfers files (port 20 for active mode, dynamic port for passive mode).

4.2 FTP Commands

4.3 FTP vs. SFTP/FTPS

Real-World Example: Bank File Transfers Banks use SFTP to securely transfer transaction logs between branches and the central server. Plain FTP would expose sensitive data.

5. Dynamic Host Configuration Protocol (DHCP)

5.1 What is DHCP?

DHCP (Dynamic Host Configuration Protocol) automatically assigns IP addresses, subnet masks, and DNS servers to devices on a network. It eliminates manual configuration (e.g., ipconfig /release and ipconfig /renew in Windows).

5.2 DHCP Process (DORA)

1. Discover: Client broadcasts DHCP Discover (port 67/68).
2. Offer: Server responds with DHCP Offer (proposed IP).
3. Request: Client accepts with DHCP Request.
4. Acknowledge: Server confirms with DHCP ACK + lease time (e.g., 24 hours).

sequenceDiagram
    participant Client
    participant DHCP_Server
    Client->>DHCP_Server: DHCP Discover (Broadcast)
    DHCP_Server-->>Client: DHCP Offer (192.168.1.100)
    Client->>DHCP_Server: DHCP Request (Accept)
    DHCP_Server-->>Client: DHCP ACK + Lease Time

5.3 DHCP Message Format

0                   1                   2                   3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     op (1=BOOTREQUEST, 2=BOOTREPLY)    |   htype (1=Ethernet) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|   hlen (6 for Ethernet)              |   hops (0)          |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|       xid (Transaction ID)           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|   secs |   flags (Broadcast)          |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                     ciaddr (Client IP)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                    yiaddr (Your IP) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                    siaddr (Server IP)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                    giaddr (Gateway IP)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

5.4 Real-World Example: Ncell Wi-Fi Hotspots

When you connect to Ncell’s Wi-Fi:

1. Your phone broadcasts a DHCP Discover.
2. Ncell’s router assigns an IP (e.g., 192.168.1.100) and DNS servers (e.g., 8.8.8.8).
3. You can now browse the internet without manual IP settings.

6. Protocol Layering in Action

All these protocols rely on lower layers. For example, when you load www.youtube.com:

1. Application Layer: DNS resolves youtube.com → 142.250.190.46.
2. Transport Layer: TCP establishes a connection (SYN, SYN-ACK, ACK).
3. Network Layer: IP packets route through routers (e.g., NTC’s backbone).
4. Data Link Layer: Ethernet frames transmit data to your NIC.
5. Physical Layer: Signals travel via fiber/copper to your device.

7. Common Exam Questions & Answers

Q1: Why do we need DNS when we can use IP addresses directly?

Answer:

• Human Usability: IPs (e.g., 142.250.190.46) are hard to remember vs. youtube.com.
• Scalability: DNS handles millions of domains without manual IP updates.
• Flexibility: One domain can point to multiple IPs (load balancing).
• Mobility: Devices can move (e.g., laptop switching networks) while keeping the same domain.

Q2: Differentiate between HTTP and HTTPS.

Q3: Explain the DHCP process with a diagram.

Answer: See the DORA sequence diagram above. Key steps:

1. Client broadcasts Discover.
2. Server offers an IP (Offer).
3. Client requests the IP (Request).
4. Server confirms (ACK) with lease time.

Q4: How does FTP transfer files securely?

Answer:

• Plain FTP: Unencrypted (avoid for sensitive data).
• SFTP: Uses SSH (port 22) for encryption.
• FTPS: Uses SSL/TLS (port 990) for encryption. Example: Banks use SFTP to transfer transaction files between branches.

## In the Real World

1. eSewa Payments

   • DNS: Resolves esewa.com.np to its server IP.
   • HTTPS: Encrypts your payment details (credit card numbers).
   • TCP: Ensures reliable delivery of transaction data.

2. YouTube Streaming

   • DNS: Maps youtube.com to Google’s IP.
   • HTTP/3 (QUIC): Uses UDP for faster video chunks (reduces buffering).
   • CDN: Distributes content via edge servers worldwide.

3. Ncell Wi-Fi Hotspot

   • DHCP: Assigns your phone an IP (e.g., 192.168.1.100) automatically.
   • DNS: Provides Google’s DNS (8.8.8.8) for internet access.

4. Daraz Order Processing

   • FTP/SFTP: Securely transfers order data from Daraz’s website to its warehouse system.
   • HTTP: Displays product pages to customers.

5. NEPSE Stock Trading

   • HTTPS: Encrypts buy/sell orders to prevent fraud.
   • DNS: Resolves nepse.com.np to the stock exchange server.

## Exam Tip

What Examiners Look For

1. Definitions: Know exact terms (e.g., "DNS is a hierarchical, distributed database").
2. Diagrams: Draw sequence diagrams for DNS/HTTP/DHCP and packet formats for HTTP headers.
3. Real-World Links: Relate protocols to Nepali examples (eSewa, Ncell, Daraz).
4. Comparisons: Tables for HTTP/HTTPS, FTP/SFTP, TCP/UDP.
5. Troubleshooting: Explain why a site loads slowly (e.g., "DNS cache miss" or "HTTP 500 error").

Common Mistakes to Avoid

• Mixing layers: Don’t say "DNS works at the transport layer" (it’s application layer).
• Ignoring ports: Always mention ports (e.g., HTTP=80, HTTPS=443).
• Overlooking security: HTTPS is not just HTTP + S; it’s TLS encryption.
• Skipping steps: For DNS, list all 4 steps (root → TLD → authoritative).

Sample Short-Answer Questions

Final Note: Master the flowcharts, packet formats, and real-world ties (eSewa, YouTube, Ncell). Examiners love practical examples!