Next: DHCP and DNS Basics

CompTIA Network+ • Lesson 3

DHCP and DNS Basics

IP addresses let devices participate on a network, but two other services make modern networking practical: DHCP helps devices get addressing automatically, and DNS helps humans use names instead of memorizing IP addresses.

Automatic Addressing Name Resolution Quiz + Rationales
By the end of this lesson
  • Understand what DHCP does
  • Understand what DNS does
  • Recognize why these services matter in real life
  • Spot basic DHCP vs DNS failure patterns
  • Strengthen Network+ troubleshooting thinking
Core service

What Is DHCP?

DHCP stands for Dynamic Host Configuration Protocol. Its job is to automatically give devices network settings such as an IP address, subnet mask, default gateway, and often DNS server information.

Simple definition:

DHCP automatically hands out network settings so devices can join the network without manual setup.

  • Without DHCP, many devices would need manual IP setup.
  • That would be slow, error-prone, and hard to manage at scale.
  • Most home and office user devices rely on DHCP every day.
Core service

What Is DNS?

DNS stands for Domain Name System. Its job is to translate human-friendly names like example.com into IP addresses that computers use to find each other.

Simple definition:

DNS is like the internet’s phone book for names and IP addresses.

  • Humans remember names better than numbers.
  • Applications often rely on DNS before they can connect to remote services.
  • DNS failures can make the internet feel “broken” even when the network path still exists.
DHCP in action

Why DHCP Matters

Imagine a laptop joining a Wi-Fi network. Instead of a human typing in every addressing detail, DHCP usually handles it automatically.

Laptop Needs network settings DHCP Server Hands out settings Network Access Now communication works DHCP usually provides IP address, subnet mask, gateway, and DNS info

Without DHCP

  • Manual setup on many devices
  • More configuration mistakes
  • Harder management in larger environments

With DHCP

  • Faster onboarding for devices
  • Consistent addressing delivery
  • Much easier for homes and organizations
DNS in action

Why DNS Matters

When a user types a website name, the device usually needs DNS to figure out which IP address belongs to that name before it can connect.

User types example.com DNS Server Returns IP address Connection 93.184.216.34 DNS lets people use names while computers still connect by IP
Important distinction:

DNS does not replace IP addressing. It helps devices find the correct IP for a given name.

DHCP symptoms

What DHCP Problems Can Look Like

  • Device connects physically but gets no valid network settings
  • User cannot reach local or internet resources
  • Device may show limited or no connectivity
  • Automatic addressing did not happen correctly
Troubleshooting thought:

Ask: Did the device receive a valid IP configuration at all?

DNS symptoms

What DNS Problems Can Look Like

  • Internet path may still exist, but names do not resolve
  • Websites by name fail even though connectivity partly works
  • Some apps cannot find remote services
  • Users often describe this as “Wi-Fi works but nothing loads”
Troubleshooting thought:

Ask: Is this a name-resolution problem instead of a full connectivity problem?

Compare them clearly

DHCP vs DNS

Service Main job Helps with Failure feel
DHCP Automatically assigns network settings Getting devices configured to join the network Device may never get valid addressing
DNS Translates names into IP addresses Finding websites and services by name Names fail even when some connectivity exists
Fast memory hook:

DHCP = “Give me my settings.”
DNS = “Tell me what IP this name belongs to.”

Real world

New Laptop on Wi-Fi

DHCP usually gives the laptop its IP settings first. Then DNS helps it reach websites by name.

Real world

Office User Can’t Browse

The issue might be no valid DHCP lease, bad DNS settings, or a broader connectivity failure.

Real world

Server by Name Fails

Users may still be on the network, but DNS trouble can stop them from finding the server by hostname.

Interactive mini drills

Quick DHCP and DNS Drills

These are meant to build instinct. Focus on the main job of each service and what failure usually feels like.

Drill 1

A new laptop joins Wi-Fi and automatically receives an IP address, gateway, and DNS information. Which service mainly handled that?

Why: DHCP is responsible for automatically providing addressing and related network settings.

Drill 2

A user types a website name, and the device needs to figure out its IP address. Which service is involved?

Why: DNS resolves a human-readable name into the IP address needed for connection.

Drill 3

A device has joined the network physically, but appears to have no valid address information. Which type of problem should you suspect first?

Why: If valid network settings were not assigned, DHCP deserves early suspicion.

Drill 4

A user says, “I seem connected, but websites by name won’t open.” What type of issue fits best?

Why: That symptom often points toward name resolution trouble rather than total loss of connectivity.
Remember this

Foundational Questions to Ask

  • Did the device receive valid network settings?
  • Is the device using automatic or manual addressing?
  • Can it reach anything locally or remotely?
  • Is the problem total connectivity or just name resolution?
  • Could the DNS information be wrong or unavailable?
Troubleshooting habit

What Strong Beginners Start Doing

  • Separate DHCP failures from DNS failures
  • Think step by step: address first, name resolution second
  • Avoid guessing that “internet is down” too early
  • Notice whether the user can reach anything at all
  • Use symptoms to narrow the service that may be failing
Lesson quiz

Network+ Lesson 3 Quiz

Score at least 75% to unlock the next lesson CTA.

1) What is the main job of DHCP?

Rationale: DHCP exists to automatically provide devices with network configuration such as IP address, subnet mask, gateway, and often DNS information. The wrong answers mix in tasks handled by DNS or other network functions.

2) What is the main job of DNS?

Rationale: DNS resolves human-readable names into IP addresses so systems can connect correctly. DHCP assigns settings; DNS helps find the right IP for a name.

3) A new device joins Wi-Fi and receives its network settings automatically. Which service most likely handled that process?

Rationale: DHCP is the service that automatically hands out addressing details. DNS comes later when the device needs to resolve names like websites or hostnames.

4) A user says, “I seem connected, but websites by name will not load.” Which service deserves suspicion?

Rationale: This is classic name-resolution language. The user may still have some connectivity, but DNS could be failing to translate names into usable IP addresses.

5) Which set of information is DHCP commonly associated with providing?

Rationale: DHCP commonly delivers the full basic network configuration a client needs to communicate properly. The other answers are unrelated to host addressing.

6) Which statement best separates DHCP from DNS?

Rationale: This is the cleanest summary. DHCP handles automatic configuration, while DNS handles name resolution. Swapping them is a very common beginner mistake, which is why this distinction matters.
Need 75% or higher to unlock the next lesson.
Lesson marked complete.

Suggested Next Page

Next, move into ports and protocols so learners understand what kinds of traffic are flowing across the network and what services commonly use them.

Next: Ports and Protocols Basics