Year 11 · Original DASKEREL study pack · Academic review pending
How network packets reach a service
Allow up to 60 minutes for reading, practice and review · Source route: Oak AQA Computer Science · DASKEREL teaching requires board review
DASKEREL wrote this resource using the Oak National Academy unit sequence as a curriculum reference. It is a study pack, not a complete unit or an exam-board-approved course. Academic review remains pending.
You will learn to
- Distinguish a local network from an internet route.
- Explain the roles of IP address, router, DNS and packet.
- Diagnose a simple connection problem using staged evidence.
Key terms: LAN · router · IP address · DNS · packet · protocol
Learn the idea
A local area network joins devices in a limited area; the internet joins many networks. A client requesting a website needs a route to a server. The web address is a human-readable name, while an IP address identifies the destination used for routing.
DNS resolves a domain name to an IP address. A router forwards packets between networks according to destination information. Packets carry parts of the data and are reassembled at the receiving end. They may take different routes; a single broken path need not stop all traffic.
Protocols give shared rules for communication. For a web request, the browser first needs name resolution and network reachability, then exchanges application data using the appropriate web protocol. HTTPS adds encrypted transport for the web exchange, but it does not mean every website or user is trustworthy.
To diagnose a failure, separate layers of evidence: does the device have local connectivity, can it reach an IP address, can DNS resolve the domain and can the service respond? A DNS failure may prevent access by name even when the remote IP route still works. Do not assume that every outage is a failed router.
Worked example
A laptop opens a school intranet by its IP address but not by its domain name. What should be checked first and why?
- The successful IP request shows local connectivity and a route to that server are likely working.
- The domain request adds a name-to-address lookup stage.
- Check whether DNS returns the expected IP address for the domain.
- Check the configured DNS server or spelling if resolution fails; verify the service separately if the lookup succeeds.
DNS is the first likely fault area; the evidence does not prove every network component is healthy.
Try together
A device cannot reach any outside IP address but can reach another device on its LAN. Which stage deserves attention?
- Local communication is working.
- Traffic leaving the LAN needs a gateway/router and onward route.
- DNS is not needed to reach a numeric IP address.
Show guided answer
Investigate the default gateway/router and upstream connection before DNS; local LAN success narrows the fault.
Practise independently
- State one job of DNS and one job of a router in a web request.
Show answer and reasoning for question 1
DNS maps a domain to an IP address; a router forwards packets between networks towards a destination. The two jobs are distinct: naming versus forwarding.
- Why can packets in one transfer arrive out of order?
Show answer and reasoning for question 2
They may take different routes or experience different delays and are reordered/reassembled at the destination. Packet switching does not guarantee identical path or travel time for every packet.
- A device can reach a public IP address but every domain lookup fails. Which component should you check first, and why?
Show answer and reasoning for question 3
Check DNS configuration or service first. The successful numeric-IP route suggests forwarding works; the added name-to-address resolution step is the likely failure point.
DASKEREL exam-style practice · 6 draft marks
This original practice task and guidance are not an official examination-board paper or mark scheme.
A college browser reports that courses.example cannot be found, but a known external server responds when addressed by IP. Explain a likely cause, identify two checks and describe how data would reach the server after the fault is fixed.
Show draft mark guidance
- Identify likely DNS/name-resolution failure (1).
- Check the domain spelling or DNS lookup result (1).
- Check configured DNS server or alternative resolved name (1).
- Explain DNS supplies an IP address (1).
- Explain packets are addressed/forwarded by routers between networks (1).
- Explain the server receives and reassembles data or returns response packets (1).
Check your understanding
- DNS does not carry every data packet; it supplies addressing information.
- An IP address and a domain name are not interchangeable labels with identical roles.
- HTTPS helps protect transport, but it does not certify the truth of page content.
Retrieve later: Describe the sequence from typing a domain name to receiving a response, naming DNS and a router.
Next step: Compare network topologies and protocols, then model latency, bandwidth and security trade-offs.
Library links: Oak National Academy · Network fundamentals (checked 2026-11-06) · DASKEREL subject library. Oak's applicable post-2022 content licence is OGL v3.0; some source assets have separate third-party rights. No Oak media is embedded here. DASKEREL is not affiliated with Oak.