IB COMPUTER SCIENCE | A2.2.2 Servers (HL Only)

Lesson objective

Describe DNS, DHCP, file, mail, proxy and web servers, considering their function, scalability, reliability and security. HL only.

Learn

A2.2.2 | FUNCTION OF SERVERS (HL ONLY)

01 | ONE SCHOOL MORNING, SIX DIFFERENT SERVICES

You open your laptop, connect to the school network, load a lesson, open a shared worksheet and send your teacher a message. It feels like one connected experience, but several services are doing different jobs behind the scenes.

A server is software that provides a service to clients, or the computer hosting that software. A client requests or uses a service. A laptop can be a client of several servers during one task, and a server can itself act as a client when it requests another service.

The six roles in this HL-only lesson are DNS, DHCP, file, mail, proxy and web servers. Learn what each service supplies, then consider how it can cope with growth, remain dependable and protect its users.

A server is not defined by having a large black case in a locked room. Services can run on dedicated hardware, virtual machines, containers or managed cloud infrastructure. One physical machine can host several roles, while one busy service can be distributed across many machines.

02 | REQUEST, PROCESS, RESPOND

A client sends a request using an agreed protocol. The server receives it, processes it according to its configuration and permissions, then returns a result or error. For example, a file service might check whether your account can read a worksheet before returning its contents.

The client and server roles describe a particular interaction. A school mail server can accept a message from your mail client and then act as a client when it contacts another mail server. This is normal cooperation, not a contradiction.

Server services need resources: processor time, memory, network capacity, storage and sometimes other services. A slow web page can therefore result from a busy database or an overloaded link rather than the web server’s CPU alone.

In the examples below, separate role boxes show separate responsibilities. They do not require six separate physical computers. Keeping that distinction clear helps you explain both functions and dependencies.

03 | DHCP SERVER: HELP A DEVICE JOIN THE NETWORK

When a new laptop joins a network, it needs usable IP configuration. A Dynamic Host Configuration Protocol (DHCP) server can allocate an address from a configured pool and supply settings such as a subnet mask, default gateway and DNS server addresses.

For DHCPv4, a common initial exchange is Discover, Offer, Request and Acknowledgement. The offer proposes configuration; the acknowledgement confirms the selected lease. A lease is a time-limited allocation, so the client must renew it or otherwise follow the protocol’s rules when it expires.

This avoids manually entering settings on every student device. A reservation can be used to allocate a chosen address to a recognised client, while still managing it through DHCP. Reservations are not the same as manually configuring a static address on the client.

The server needs an adequate address pool and consistent management. An exhausted pool can prevent new allocations even if the server is running. A second independently configured server with an overlapping pool is not automatically a safe backup: allocations must be coordinated to avoid conflicts.

04 | DNS SERVER: FIND INFORMATION ABOUT A NAME

You remember a name such as portal.example more easily than an IP address. A Domain Name System (DNS) server answers questions about domain names, commonly helping resolve a host name to an IP address. DNS also stores other record types, including information used to route mail.

A recursive resolver obtains an answer for a client, using a valid cached answer or querying other DNS servers when needed. An authoritative server supplies the records for the zones it serves. These are different DNS roles, even though introductory diagrams often draw one DNS box.

A cache keeps reusable answers temporarily. A record’s time-to-live helps limit how long it can be reused. Caching reduces repeated work and can allow some lookups to continue during a short upstream interruption, but it does not make all names available indefinitely.

DNS normally supplies information needed to contact a service. It does not send the actual worksheet or web page to the browser. A DNS failure can stop a new name lookup while an existing connection or a valid cached answer still works.

05 | KEEP DHCP AND DNS DISTINCT

QuestionRelevant roleWhat it does not mean
What configuration can this laptop use on this network?DHCP supplies a lease and related settingsIt has not downloaded the requested lesson
What address is associated with portal.example?DNS answers a name queryIt has not assigned the laptop its own DHCP lease
Can I request the lesson resource now?The browser contacts the web service using the resolved informationDNS does not carry every subsequent web request

DHCP can tell the laptop which DNS resolver to use. That connection between the services is why students sometimes mix them up. Think of DHCP as helping configure the client and DNS as answering name-related questions.

These are common arrangements, not the only ways to configure or discover services. A device can have valid manually configured settings, and applications may already have cached information. Do not assume every page request begins with a fresh DHCP exchange and a fresh DNS lookup.

06 | FILE SERVER: SHARE AND CONTROL STORED FILES

A file server provides network access to files and folders. Students might open a shared worksheet, save coursework to a personal area or collaborate using an agreed folder structure. Protocols such as SMB support network file access.

Central storage can simplify permission management, quotas and backups. A quota limits storage consumption; an access permission controls actions such as reading, editing or deleting. Authentication identifies a user, while authorisation decides what that user may do.

Simultaneous access needs appropriate handling. File services and applications may use locking or other coordination to reduce conflicting changes, but simply placing a document in a shared folder does not guarantee safe real-time co-editing in every application.

A file server also creates dependencies. If the service, storage or connection fails, users may lose access. Redundant storage can help with some hardware faults, while separate, protected backups support recovery of deleted or damaged data. RAID is not a backup: it does not by itself recover an earlier version overwritten by mistake or malicious software.

07 | MAIL SERVER: ACCEPT, TRANSFER AND STORE MESSAGES

A mail server handles email services. A user submits a message; mail infrastructure transfers it toward the recipient’s domain; a receiving service stores it in a mailbox. The recipient then accesses their messages using a mail client or webmail.

SMTP is used for message submission and transfer. IMAP provides access to and management of messages held in a mailbox; POP3 is another retrieval approach. Webmail presents a browser interface over HTTP/HTTPS while mail services handle the messages behind it.

If a destination is temporarily unavailable, a sending mail server can queue a message and retry according to its policies. This supports store-and-forward delivery, but it does not guarantee immediate delivery or mean every undeliverable message stays queued forever.

Security includes protecting accounts, checking permissions to send, filtering suspicious content and limiting abuse. An open relay lets unauthorised third parties relay mail and can be abused for spam. Transport encryption protects a connection when used; it is not automatically end-to-end encryption between the human sender and recipient, nor proof that a message is trustworthy.

08 | WEB SERVER: ANSWER HTTP REQUESTS

A web server handles HTTP requests and returns responses containing resources or results. It can return HTML, CSS, JavaScript, images and other data. A response also includes control information such as an HTTP status code.

Some resources are static: the server supplies existing content. Other responses are dynamic: application code constructs a result, perhaps using a database. The web server and application runtime may be separate components or work together on the same host.

For example, opening a school timetable can involve a request, authentication, a database query and an HTML response. The database stores and queries structured data; it is not the same role as the web server receiving the HTTP request.

A busy web service can distribute requests among multiple instances, cache eligible content or add resources to an existing instance. Those changes help only if shared dependencies, session handling, data consistency and security are also designed appropriately.

09 | PROXY SERVER: AN INTERMEDIARY WITH A PURPOSE

A proxy server handles communication on behalf of another party. A forward proxy acts for clients when they access other services. A school might use one to apply access policies, record permitted connection information or cache eligible responses.

A reverse proxy sits in front of backend services and acts for them. It can receive incoming web requests, route them to suitable backends, terminate TLS where configured, cache eligible responses or help balance requests. “Forward” and “reverse” describe which side the proxy represents.

Caching needs rules. Private or personalised responses must not be shared with other users, and stale content may need revalidation or replacement. A cache can reduce repeated transfers, but cannot safely treat every response as public and reusable.

A proxy does not automatically provide anonymity, block every threat or read all encrypted content. An ordinary HTTPS tunnel does not expose the application contents to the proxy. Inspecting protected content requires an explicitly configured trust and interception arrangement; terminating TLS at a reverse proxy also means securing its onward connection appropriately.

10 | SEE THE TWO PROXY ROLES

FORWARD PROXY | ACTS FOR CLIENTS

School clientSchool forward proxyExternal service

The client uses an intermediary to reach other services.

REVERSE PROXY | ACTS FOR SERVICES

Visitor’s clientService’s reverse proxySelected backend

The service presents an intermediary in front of its backends.

Both diagrams show request direction; responses return through the corresponding intermediary. A proxy is a service role. A particular product can combine several proxy features, but its actual configuration determines which functions it performs.

Compare this with a router: ordinary routing forwards IP packets toward a next hop. A proxy handles a connection or application exchange on behalf of another party. They are related parts of a network path, but not interchangeable definitions.

11 | FOLLOW A LAPTOP FROM CONNECTION TO A LESSON

Assume the laptop needs a new DHCPv4 lease, has no usable DNS answer cached and accesses a permitted static lesson through a configured forward proxy. The model separates configuration, lookup, policy checking and web delivery.

For clarity, it shows the proxy performing the origin name lookup after receiving a request naming the destination, and an eligible public response being cached. DNS lookup location varies by proxy arrangement. These stages are a specified example, not a required sequence for every website or HTTPS tunnel.

12 | SCALABILITY: HANDLE MORE USERS AND MORE WORK

Scalability is the ability to handle growth while maintaining acceptable service. More simultaneous clients can increase processor load, memory use, storage operations and network demand. The limiting resource differs between server roles.

Vertical scaling adds resources to an instance, such as memory or processor capacity. Horizontal scaling adds instances and distributes work. Adding instances is not automatic: shared state, load distribution and consistency can make it more complex.

For DNS, caching and multiple service instances can reduce or distribute query work. For DHCP, enough addresses and coordinated allocation matter as much as processing capacity. For file and mail services, storage size, storage performance and simultaneous access can become important constraints.

For web and proxy services, load distribution and safe caching can reduce repeated backend work. However, ten web instances waiting on one overloaded database can still be slow. Measure the actual bottleneck before choosing an expansion.

13 | RELIABILITY: KEEP THE SERVICE AVAILABLE AND RECOVERABLE

A reliable service needs more than a powerful machine. It needs appropriate hardware, monitoring, maintenance and recovery arrangements. Redundancy supplies alternatives for selected failures; failover transfers work to a working alternative. Both need to be configured and tested.

A replicated service can remain available after an instance fails, but replication is not a substitute for a backup. Deletion or corruption can be replicated too. A backup preserves recoverable data from a point in time; restoration testing checks whether it can actually be used.

Different services have different failure effects. A DHCP outage may affect new allocations or later renewals while valid existing leases continue until their rules require action. DNS caching may temporarily preserve some lookups. A file server outage can directly block access to stored work.

Also examine common dependencies. Two servers in the same failed power circuit, behind the same broken network link or using the same failed storage can stop together. A plan should state which failures it covers and how much interruption or data loss can be tolerated.

14 | SECURITY: IDENTITY, PERMISSIONS AND SAFE OPERATION

Server security protects confidentiality, integrity and availability. Confidentiality concerns who can see information, integrity concerns unauthorised changes, and availability concerns access when needed. These aims can conflict with convenience if permissions are too broad.

Start by limiting exposed services, patching supported software, protecting administration and applying least privilege. Authenticate users where required, authorise the permitted actions and protect relevant traffic with appropriate encryption. Logs and monitoring help detect problems, but logs themselves can contain sensitive information.

Apply controls to each role. Protect DNS administration and records; prevent unauthorised DHCP service or configuration changes; restrict file access; secure mail accounts and relaying; enforce appropriate proxy policy and cache separation; validate web inputs and access rules.

No single control makes a server secure. HTTPS does not fix a broken authorisation check. A firewall does not replace patching. Backups need protection and tested recovery, because an attacker may try to damage them as well as the live service.

15 | COMPARE THE SIX SERVICES

ServerFunctionGrowth considerationReliability considerationSecurity consideration
DNSAnswers name-related queriesQuery demand, caching and service distributionMultiple resolvers/authoritative services as appropriate; caches have limitsProtect records/admin; validate DNS data where supported
DHCPManages address leases and host settingsPool size, clients and allocation loadCoordinate failover/leases; avoid conflicting allocationsControl authorised servers and configuration
FileProvides access to shared files/foldersStorage capacity, I/O and concurrent usersRedundancy plus independent protected backupsAuthentication, file permissions and least privilege
MailSubmits, transfers and stores messagesMailbox storage, traffic, filtering and queuesRecovery for mailboxes/queues; temporary retry has limitsAccount security, safe relay policy and filtering
ProxyIntermediates access for clients or servicesConnection demand and safe cachingAlternative instances and backend dependenciesAccess policy, private cache separation and protected links
WebHandles HTTP requests and responsesInstances, bandwidth, application/database capacityLoad distribution, health checks and recoverable dataTLS, patching, input handling and access control

This table is a comparison aid after the explanations. In an answer, connect a design choice to its purpose: “The file server checks permissions so that students can read shared worksheets while only authorised staff can alter them.”

16 | CHOOSE THE SERVICE AND EXPLAIN ITS JOB

Use each situation to identify the service most directly responsible. Several services may cooperate in the full system, so focus on the specific function described.

17 | INVESTIGATE A SERVICE FAILURE

Choose a service that becomes unavailable in the stated conditions. The model describes likely immediate consequences; it does not claim to diagnose every real outage from one symptom. Supporting network and server components are assumed healthy unless stated.

18 | DESCRIBE THE ROLE, THEN CONNECT IT TO A NEED

For describe, state the service’s main characteristics and function. “It manages the network” is too vague. Specify the request it handles and what result it supplies, then add the relevant scalability, reliability or security consequence.

For example: “A DHCP server allocates time-limited IP address leases and supplies settings such as the gateway and DNS resolver address. This reduces manual configuration for many clients. Its address pool must be large enough, and any failover arrangement must coordinate leases to avoid conflicting allocations.”

Or: “A file server provides shared network file access. It checks permissions so that users can perform only authorised actions. Growth requires enough storage and access capacity, while protected backups and tested recovery help restore lost or damaged files.”

The next lesson compares client-server and peer-to-peer models. Here, be confident about the six roles and the difference between service function, capacity, dependable operation and protection.

MATCH THE SERVER IDEA TO ITS FUNCTION

Terminology

Terminology

Server

Software providing a service to clients, or a host running that software.

Client

A program or device requesting or using a service.

Server role

A specific service responsibility; several roles can share a host.

DNS server

A server answering Domain Name System queries.

Recursive resolver

A DNS service obtaining answers for clients using cache or other DNS servers.

Authoritative DNS server

A DNS service supplying records for zones it serves.

DNS cache

Temporarily retained DNS answers for reuse within applicable rules.

DNS TTL

A value limiting how long a DNS record may be cached.

DHCP server

A service managing address leases and supplying host configuration.

Address pool

A configured set of addresses available for allocation.

Lease

A time-limited allocation of an address and associated configuration.

DHCP reservation

A configured allocation of a chosen address to a recognised client through DHCP.

File server

A service providing network access to files and folders.

Quota

A limit on a user’s or group’s resource consumption, such as storage.

Authentication

Checking an identity claim.

Authorisation

Deciding which actions an identified party is allowed to perform.

Mail server

A service handling functions such as message submission, transfer and mailbox storage.

SMTP

A protocol for mail submission and transfer.

IMAP

A protocol for accessing and managing messages in a mailbox.

Mail queue

Messages awaiting a processing or delivery attempt.

Proxy server

An intermediary handling communication on behalf of another party.

Forward proxy

A proxy acting for clients accessing other services.

Reverse proxy

A proxy acting in front of backend services.

Web server

Software handling HTTP requests and responses.

Static content

Existing resource content supplied rather than generated for that request.

Dynamic content

Content constructed by application processing, often using other services.

Vertical scaling

Adding resources to an instance.

Horizontal scaling

Adding instances and distributing work across them.

Failover

Moving work to a working alternative after a failure.

Backup

A recoverable copy of data from a point in time, separate from live redundancy.

Questions

Questions

CHECK YOUR UNDERSTANDING

Select all correct choices. Each exact set earns one point.

1. Which describe server roles correctly?
2. Which are DHCP functions?
3. Which describe DNS?
4. Which describe file services?
5. Which describe mail services?
6. Which are web-server roles?
7. Which describe proxies?
8. Which are scalability concerns?
9. Which support dependable operation?
10. Which distinguish security controls?

EXPLAIN AND COMPARE

Write your answers before revealing each sample.

1. Describe the function of a server and its relationship with a client.

2. Describe the function of a DHCP server.

3. Describe the function of a DNS server.

4. Compare DNS and DHCP in a laptop connection example.

5. Describe a file server’s function and one security requirement.

6. Describe the functions of mail services and relevant protocols.

7. Describe the function of a web server using a dynamic page example.

8. Compare forward and reverse proxy roles.

9. Explain why adding web instances may not resolve poor performance.

10. Explain why replication is not the same as a backup.

11. Describe the effect of a DHCP outage on different clients.

12. Suggest reliability and security measures for a school file service.

DESIGN IT | SERVICES FOR A GROWING SCHOOL

A school is adding 200 devices and needs reliable lesson access, shared coursework folders and email. Identify where each of the six server roles could contribute. For three selected roles, describe a growth constraint, a failure consequence and a relevant security control. Explain which services might share a host and which shared dependencies would still need attention.

Flashcards

Flashcards

Click to flip. Select the ideas you need to revisit.

0 cards selected for revision.

    Selections are kept while this page is open.

    Workbook

    Workbook

    COMING SOON

    The workbook for A2.2.2 Servers (HL Only) is coming soon. Complete the matching task and written questions in your exercise book.