Challenge 2: Two Domains, One IP, Identical Content — What's Missing — Solution Walkthrough

What the user has actually done:

Pointing two domains at the same IP address via DNS only accomplishes
the first half of serving two different sites — it gets requests for
either domain to the same physical server. DNS itself has no concept
of "sites" at all; it simply answers "this domain name resolves to
this IP address," for both domains identically.

What's actually missing:

The web server itself has not been configured with two separate
VirtualHosts, server blocks, or Sites — one per domain, each pointing
at its own DocumentRoot/root/content. Without that, the server likely
has only a single default site (or a single VirtualHost with no
ServerName matching set up at all), which answers every request
identically regardless of which Host header it received, since there's
no per-domain configuration for the server to match against.

The fix:

Configure a separate VirtualHost/server block/Site for each domain, as
covered in this chapter, so the web server itself performs the actual
split the user was expecting DNS to handle.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise directly targets the exact misconception this chapter's
own warning box calls out — DNS resolves names to an IP, but the
per-domain split is the web server's own job, not something that
happens automatically just because two domains point at the same
address.