DEV Community

Tejas Shinkar
Tejas Shinkar

Posted on

Network Protocols — ARP, FTP, SMTP, HTTP, HTTPS, DNS and DHCP

🌐 Network Protocols

ARP, FTP, SMTP, HTTP, HTTPS, DNS and DHCP

Series: Networking Fundamentals for Cloud & DevOps

We have already seen how hosts, switches, routers, MAC addresses and IP addresses work together. Now we move one level higher and look at the protocols that define how different types of communication happen.


1. Protocol

A protocol is a set of rules/messages that devices follow to communicate.

Think of a protocol as a common language with defined rules.

For example:

  • If two devices need to resolve an IP address to a MAC address → ARP
  • If a client needs to transfer a file → FTP
  • If a client needs to send an email → SMTP
  • If a browser needs web communication → HTTP/HTTPS
  • If a host needs to convert a domain name into an IP address → DNS
  • If a host needs its network configuration automatically → DHCP

A quick overview:

Protocol Full Form Main Job
ARP Address Resolution Protocol IP → MAC
FTP File Transfer Protocol Transfer files
SMTP Simple Mail Transfer Protocol Send email
HTTP HyperText Transfer Protocol Web communication
HTTPS HTTP Secure Secure HTTP using TLS
DNS Domain Name System Domain name → IP
DHCP Dynamic Host Configuration Protocol Automatically gives network configuration

The important thing is not just memorizing the names.

Each protocol solves a different communication problem.


2. ARP

ARP = Address Resolution Protocol

ARP solves this problem:

"I know the IP address, but what is the MAC address?"

Suppose a host knows:

9.1.1.22
Enter fullscreen mode Exit fullscreen mode

but needs the corresponding MAC address.

It broadcasts an ARP Request:

Host 9.1.1.11:

"Who has 9.1.1.22?"
Enter fullscreen mode Exit fullscreen mode

The host with that IP responds:

Host 9.1.1.22:

"My MAC is b3b3."
Enter fullscreen mode Exit fullscreen mode

So the mapping becomes:

9.1.1.22 → b3b3
Enter fullscreen mode Exit fullscreen mode

Therefore:

ARP = IP → MAC mapping

This connects directly to what we learned earlier:

IP address
    ↓
ARP
    ↓
MAC address
    ↓
Ethernet frame
Enter fullscreen mode Exit fullscreen mode

ARP is mainly concerned with finding the Layer 2 address needed for communication on the local network.


3. FTP

FTP = File Transfer Protocol

FTP is used for file transfer.

The basic idea is:

Client ─────────────→ FTP Server
          file.pdf
Enter fullscreen mode Exit fullscreen mode

For example:

Client ── RETR file.pdf ──→ FTP Server
Client ←──── file.pdf ───── FTP Server
Enter fullscreen mode Exit fullscreen mode

RETR essentially means:

Retrieve/download this file.

So the simple memory rule is:

FTP → File transfer
Enter fullscreen mode Exit fullscreen mode

4. SMTP

SMTP = Simple Mail Transfer Protocol

SMTP is used for sending email.

Conceptually:

Client ── HELLO ───────→ SMTP Server

Client ── email ───────→ SMTP Server
Enter fullscreen mode Exit fullscreen mode

The protocol defines how the email-sending communication takes place between the client and mail server, and between mail servers.

So:

SMTP = sending mail


5. HTTP

HTTP = HyperText Transfer Protocol

HTTP is used for web communication.

A browser/client can request a resource from a web server:

Client ── GET /index.html ──→ Web Server
Client ←────── 200 OK ─────── Web Server
Enter fullscreen mode Exit fullscreen mode

The client asks for a resource, and the web server responds.

So:

HTTP → Web communication
Enter fullscreen mode Exit fullscreen mode

This is the basic protocol underneath the request/response model used by the web.


6. HTTPS

HTTPS = HTTP + TLS security

HTTPS is HTTP communication protected using TLS.

The important idea is:

HTTP
  +
TLS security
  ↓
HTTPS
Enter fullscreen mode Exit fullscreen mode

TLS provides security mechanisms such as encryption and authentication for the communication.

Conceptually:

Client ═════ encrypted HTTPS connection ═════→ Web Server
Enter fullscreen mode Exit fullscreen mode

So remember:

HTTP  = Web communication

HTTPS = Secure web communication
Enter fullscreen mode Exit fullscreen mode

HTTPS is what allows a browser to communicate with a web server while protecting the connection against unauthorized observation or modification.


7. DNS

DNS = Domain Name System

DNS solves a different problem from ARP.

ARP asks:

"I know the IP. What is the MAC?"

DNS asks:

"I know the website/domain name. What is its IP?"

Suppose you want to access:

site.com
Enter fullscreen mode Exit fullscreen mode

Your computer needs the server's IP address.

It asks a DNS server:

What is the IP address of site.com?
Enter fullscreen mode Exit fullscreen mode

The DNS server responds:

site.com → 160.8.23.154
Enter fullscreen mode Exit fullscreen mode

So:

DNS = Domain name → IP

The key distinction is:

ARP:
IP → MAC

DNS:
Name → IP
Enter fullscreen mode Exit fullscreen mode

8. Four Things a Host Needs for Internet Connectivity

A host generally needs four important pieces of network configuration:

1. IP Address
2. Subnet Mask
3. Default Gateway
4. DNS Server
Enter fullscreen mode Exit fullscreen mode

For example:

IP:
9.1.1.11

Mask:
255.255.255.0

Gateway:
9.1.1.1

DNS:
8.8.8.8
Enter fullscreen mode Exit fullscreen mode

Each one has a different job.

IP Address

Identifies the host on the network.

IP → Which host am I?
Enter fullscreen mode Exit fullscreen mode

Subnet Mask

Determines which addresses belong to the local network.

Subnet Mask → Which network am I in?
Enter fullscreen mode Exit fullscreen mode

Default Gateway

Provides the router used to reach other networks.

Default Gateway → How do I reach other networks?
Enter fullscreen mode Exit fullscreen mode

DNS

Converts domain names into IP addresses.

DNS → What IP belongs to this domain name?
Enter fullscreen mode Exit fullscreen mode

So:

IP              → identifies the host
Subnet mask     → determines the local network
Default gateway → router used to reach other networks
DNS             → converts names into IP addresses
Enter fullscreen mode Exit fullscreen mode

These four pieces work together whenever a host needs to communicate beyond its immediate network.


9. DHCP

DHCP = Dynamic Host Configuration Protocol

DHCP automatically provides network configuration to a client.

Without DHCP, a host would need to be manually configured with values such as:

IP      = 9.1.1.11
Subnet  = 255.255.255.0
Gateway = 9.1.1.1
DNS     = 8.8.8.8
Enter fullscreen mode Exit fullscreen mode

With DHCP, the client can obtain these settings automatically from a DHCP server.

The basic process is:

Client → DHCP Discover
Server → DHCP Offer
Client → DHCP Request
Server → DHCP ACK
Enter fullscreen mode Exit fullscreen mode

The four steps are commonly remembered as:

D → O → R → A

Discover
Offer
Request
ACK
Enter fullscreen mode Exit fullscreen mode

The result is that the host receives its network configuration automatically.

DHCP automatically gives a host its network configuration.


Quick Revision

ARP
→ IP → MAC

DNS
→ Name → IP

DHCP
→ IP + Mask + Gateway + DNS

HTTP
→ Web communication

HTTPS
→ Secure web communication

FTP
→ File transfer

SMTP
→ Send email
Enter fullscreen mode Exit fullscreen mode

The Big Picture

These protocols solve different problems, but they work together when a host accesses something on the Internet.

A simplified sequence could look like:

1. DHCP
   ↓
   Get IP + subnet mask + gateway + DNS

2. DNS
   ↓
   Convert domain name → destination IP

3. Routing
   ↓
   Decide whether destination is local or remote

4. ARP
   ↓
   Resolve the next-hop IP → MAC

5. HTTP / HTTPS
   ↓
   Communicate with the web server
Enter fullscreen mode Exit fullscreen mode

So don't think of these protocols as isolated terms.

They are different pieces of the same networking process:

DHCP
  ↓
Network configuration

DNS
  ↓
Find destination IP

Routing
  ↓
Find next hop

ARP
  ↓
Find next-hop MAC

HTTP / HTTPS
  ↓
Exchange web data
Enter fullscreen mode Exit fullscreen mode

And other protocols solve other application-level problems:

FTP  → File transfer
SMTP → Email
Enter fullscreen mode Exit fullscreen mode

The important mental model is:

Protocols exist because different parts of communication need different rules.


Part 6 of 6 — Networking Fundamentals for Cloud & DevOps

This completes the current networking fundamentals sequence and provides the protocol foundation needed for deeper AWS networking concepts.

Top comments (0)