Yes—one Apache server and one IP address can host several domains. The reliable pattern is name-based virtual hosting: DNS sends every domain to the server, then Apache examines the requested hostname and selects the matching <VirtualHost> block.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Create one virtual-host block for each independent website. Give every block an explicit ServerName and DocumentRoot; add ServerAlias values only for alternate names that should serve the same site. For HTTPS, create corresponding port-443 blocks and configure certificates that cover the names being served.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What “several domains on one virtual host” actually means
The phrase is often used loosely. Apache can place several domains on one server, network address, or IP, but separate websites normally use separate <VirtualHost> blocks. A single block can handle several hostnames when those names are aliases for the same site.
Name-based virtual hosting is usually simpler than assigning a separate IP address to every site. Apache first identifies the address and port that accepted the connection, then uses the hostname supplied by the request to choose among the virtual hosts attached to that address and port.
#1 Best Overall
- Independent sites: use a separate block and document root for each site.
- Alternate names for one site: keep one block and list the extra names with
ServerAlias. - HTTPS: repeat the mapping on port 443 and make sure the TLS certificate covers the requested name.
Prerequisite: point every domain at the Apache server
Apache configuration does not create DNS records. Before debugging virtual-host rules, create the DNS records that make each domain and alias resolve to the server’s address.
Records to create
- An
Arecord for each name that should resolve over IPv4. - An
AAAArecord for each name that should resolve over IPv6, when the server is reachable over IPv6. - Equivalent records from your DNS provider when it uses a different record interface or terminology.
Include the bare domain and the www name if both are intended to work. For example, a site represented by example.com and www.example.com needs both names to resolve before Apache can match both of them.
Recommended Free Tools
Confirm DNS before changing Apache
Resolve every name and compare the returned address with the server’s intended public address. If one name still points to an old host, has no record, or resolves to a different address, Apache on the correct server cannot receive that request. DNS propagation and cached answers can also make a recent change appear inconsistent; test each name separately and record which address it returns.
Choose the layout before writing configuration
The correct layout follows the relationship between the domains, not the number of names. The choices below prevent a common mistake: putting unrelated sites in one document root merely because they share an IP.
| Decision | Use this when | Operational effect |
|---|---|---|
| Separate document roots | Domains are independent websites | Each site gets its own DocumentRoot, content tree, and virtual-host block. |
| Shared content with aliases | Several names are alternate entry points for one website | One block serves the same files and lists the additional names with ServerAlias. |
| HTTP-only blocks | The service is intentionally available only on port 80 | Only *:80 mappings are needed; there is no TLS selection for that service. |
| HTTP plus HTTPS blocks | Visitors should reach the site over both protocols | Define matching port-80 and port-443 mappings and handle certificate coverage separately. |
| Explicit aliases | Multiple names should display the same site without changing the address | ServerAlias handles the names inside the same virtual host. |
| Redirects | One public name should send visitors to another canonical URL | The request is deliberately moved to a different URL rather than simply served as an alias. |
| Isolated logs and access controls | Sites have different operators, privacy needs, or security boundaries | Keep the sites’ operational records and restrictions separate. |
| Shared logs and access controls | One team administers the sites under a common policy | Centralized handling is simpler, but an incident or policy change can affect all sites. |
Do not use an alias to hide that two sites are independent. If they need different files, permissions, access rules, or operational ownership, give them different blocks and roots.
Rank #2
- Used Book in Good Condition
Create the HTTP virtual hosts
For a basic HTTP setup, add one <VirtualHost *:80> block for each distinct website. Apache requires an explicit ServerName and a DocumentRoot in each name-based virtual host. Add aliases only where they belong to that same site.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall<VirtualHost *:80>
ServerName example.com
ServerAlias www.example.com
DocumentRoot /var/www/example
</VirtualHost>
<VirtualHost *:80>
ServerName example.net
ServerAlias www.example.net
DocumentRoot /var/www/example-net
</VirtualHost>What each directive does
<VirtualHost *:80>groups rules for requests received on port 80 on any local address.ServerNameis the primary hostname Apache should match for that site.ServerAliasadds other hostnames that should reach the same document root.DocumentRootidentifies the files Apache serves for the block.
Replace the example names and paths with your real domains and directories. Keep each independent site’s files in its own root. A typo in a hostname or path can make a valid request land in the wrong block or return content from an unexpected directory.
One site with several names
If several domains are simply alternate names for one website, place them in one block as aliases rather than duplicating the document root. The primary name belongs in ServerName; the other names belong in ServerAlias. This keeps one content location while making the intended hostname list visible in the configuration.
Several independent sites
Give every independent site its own block, primary name, and document root. This is the arrangement shown for example.com and example.net above. It also makes later changes safer: changing one site’s files or rules does not silently replace another site’s content.
How Apache decides which site to serve
Understanding the selection order explains most “wrong site” reports.
- Apache groups configured virtual hosts by the local address and port that received the connection.
- For HTTP, it compares the request’s
Hostheader with theServerNameandServerAliasvalues in that group. - For an SSL connection, the TLS SNI hostname participates in selecting the HTTPS virtual host; the certificate presented during the TLS handshake must also cover the requested name.
- Apache processes matching name-based hosts in configuration order. When more than one entry could match, the first matching name is used.
- If no
ServerNameorServerAliasmatches, the first virtual host listed for that address-and-port pair becomes the fallback.
The fallback rule is why a request can show a real website even though its hostname was never configured: Apache is serving the first block for that address and port. Treat the first block as an intentional default, not as an accidental place to store a site.
Why the same IP is enough
With name-based hosting, the IP address identifies the Apache server, while the hostname identifies the site inside Apache. The domains do not need separate IPv4 addresses merely because they have separate virtual hosts. They do, however, need DNS records that lead the request to that server.
Add HTTPS without mixing up TLS and virtual-host mapping
HTTPS requires the same hostname-to-site plan plus TLS configuration. Define corresponding <VirtualHost *:443> blocks for the HTTPS names you intend to serve.
Port 443 blocks
Each HTTPS block should identify its site with an explicit ServerName, list any same-site aliases with ServerAlias, and point at the intended content. Keep the port-80 and port-443 hostname sets aligned unless you deliberately want different behavior for the two protocols.
Apache uses the request’s SNI hostname to select among HTTPS virtual hosts after selecting the address and port. A certificate is a separate requirement: it must cover the hostname the browser requests. A correct virtual-host match cannot compensate for a certificate that omits that name.
Certificate strategy
Choose a certificate arrangement that covers every HTTPS name: a certificate can cover one name or multiple names, depending on the certificate you obtain. Certificate issuance, storage, and renewal are separate operational tasks from Apache’s virtual-host mapping. Test renewal independently so a future certificate change does not leave one alias mismatched.
HTTP and HTTPS are separate listeners
A working *:80 block does not automatically create a working *:443 site. Configure and verify both address-and-port groups. If HTTP works but HTTPS shows the wrong content, inspect the port-443 order, the SNI name, and certificate coverage rather than changing the port-80 block.
Verify Apache’s parsed configuration
Do not rely on the file you edited alone; verify the configuration Apache actually parsed. On Unix-like systems, run:
apachectl -SOn Windows, use:
httpd.exe -SThe dump should show the address-and-port groups, every ServerName and ServerAlias, the order in which the hosts were read, and the default host for each group. Compare that output with your intended design.
Verification sequence
- Confirm each domain and alias resolves to the intended server address.
- Check that every independent site has its own
ServerNameandDocumentRoot. - Check that aliases appear under the block whose content they should serve.
- Run the appropriate configuration-dump command and inspect the reported order and fallback host.
- Test HTTP names individually, then test HTTPS names individually.
- For an HTTPS failure, inspect both the selected virtual host and the certificate presented for the SNI hostname.
Use a deliberately unique test file in each document root while validating. A distinctive response makes it obvious which root Apache selected and avoids confusing identical default pages.
Best Value
- Used Book in Good Condition
Troubleshoot a domain that shows the wrong site
| Symptom | Likely cause | What to inspect | Correction |
|---|---|---|---|
| Every domain shows the same site | The requested name is not matching a configured host, so the first host is acting as fallback | DNS result, exact Host name, and apachectl -S or httpd.exe -S output |
Add the missing ServerName or ServerAlias, or correct the DNS record. |
| Only one alias fails | The alias is absent or attached to another block | The spelling of the hostname and the block containing ServerAlias |
Put the alias in the block for the intended site. |
| HTTP is correct but HTTPS is wrong | The port-443 group has different order or hostname coverage | The HTTPS blocks, SNI hostname, and certificate | Align the 443 mapping with the intended site and use a certificate covering that name. |
| A domain reaches another server | DNS still points elsewhere | The resolved A/AAAA address for the domain | Update the DNS record and wait for caches to expire before retesting. |
| A newly edited block has no effect | Apache parsed a different file or configuration order than expected | The configuration dump rather than only the source file | Find the loaded block, correct the active configuration, then verify the parsed result again. |
| Two sites share files unexpectedly | They use the same DocumentRoot or were placed under one alias block |
The document-root paths and relationship between the domains | Separate the roots and blocks when the sites are independent. |
Check the hostname actually sent
A browser’s visible URL is not enough when diagnosing a proxy, redirect, or test tool. Inspect the HTTP Host header that reached Apache. For HTTPS, also establish which SNI hostname was sent during the TLS handshake. A mismatch between the intended name and the name delivered to Apache produces a correct fallback response from Apache’s point of view.
Check order before rewriting everything
If the dump shows the expected names but the response is still wrong, inspect the order of the blocks for that address and port. An earlier matching alias can capture a request before a later block is considered. Keep aliases narrow and avoid listing a name in more than one site.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Aliases, canonical names, and redirects
ServerAlias is a hostname-to-the-same-site mapping. It lets two names serve one document root while preserving the requested URL. A redirect is a different decision: it tells the client to request another URL, usually to establish one canonical public name.
Choose an alias when both names are valid entry points for the same site. Choose a redirect when only one name should remain public or when you need the browser, search engine, and links to converge on a canonical address. Do not list a name as an alias in one block and redirect it from another block; that creates an avoidable ordering conflict.
Logging and access-control boundaries
Shared content does not automatically mean shared operations. Decide whether the domains need isolated or shared logging and access controls before deployment.
When to isolate
- Different sites have different administrators or users.
- One site may need stricter access restrictions than another.
- You need to attribute requests, incidents, or resource use to a specific site.
- A change for one domain must not alter another domain’s records or protections.
When sharing is reasonable
Shared handling can be simpler when one team owns every site and applies one policy. Make the choice deliberate: a common policy means a configuration mistake or access change can affect all domains in the group.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteA practical deployment checklist
- List every public hostname, including bare and
wwwforms that should work. - Mark each hostname as an independent site, an alias, or a name that should redirect.
- Choose a document root for each independent site.
- Create the required A, AAAA, or equivalent DNS records and confirm they resolve to the Apache server.
- Write one explicit port-80 virtual-host block per independent site.
- Put same-site alternate names in
ServerAliasrather than creating duplicate roots. - Create corresponding port-443 blocks for HTTPS names.
- Obtain and maintain certificate coverage for every HTTPS hostname.
- Run
apachectl -Sorhttpd.exe -Sand verify names, paths, order, and defaults. - Test each hostname over HTTP and HTTPS, checking the delivered
Hostand SNI names when a result is unexpected. - Review logging and access-control boundaries so the operational design matches the ownership of the sites.
Common design mistakes to avoid
- Expecting Apache to create DNS: virtual-host blocks only describe how Apache handles requests that reach it.
- Using one block for unrelated websites: aliases are for alternate names of one site, not a substitute for separate roots.
- Omitting
ServerName: an explicit primary name makes matching and diagnostics predictable. - Forgetting port 443: an HTTP mapping does not configure HTTPS.
- Ignoring the first-host fallback: unmatched names will still receive the first block for the address and port.
- Checking only a browser page: inspect the parsed configuration, DNS result, and delivered hostname when the response is surprising.
- Treating certificates as virtual-host rules: correct matching and valid certificate coverage are separate requirements.
Final perspective
Hosting several domains on one Apache server is a mapping problem with three layers: DNS sends each name to the server, Apache maps the request hostname to a virtual-host block, and HTTPS adds SNI and certificate coverage for secure connections. Keep independent sites in separate blocks and roots, use aliases only for genuinely shared content, verify the parsed order, and make the fallback host intentional. That structure scales from two domains to many without requiring one IP address per site.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
