Why virtual hosting serves multiple domains in Nginx - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the server name for a virtual host.

Nginx

server {
    listen 80;
    server_name [1];
    root /var/www/example;
}

Drag options to blanks, or click blank then click option'

A192.168.1.1

Blocalhost

Cexample.com

Ddefault_server

Attempts:

3 left

💡 Hint

Common Mistakes

Using IP address instead of domain name in server_name.

The server_name directive tells Nginx which domain this server block will respond to. Using example.com sets the virtual host for that domain.

2fill in blank

medium

Complete the code to listen on port 80 for HTTP requests.

Nginx

server {
    [1] 80;
    server_name example.com;
    root /var/www/example;
}

Drag options to blanks, or click blank then click option'

Alisten

Bserver_name

Clocation

Dproxy_pass

Attempts:

3 left

💡 Hint

Common Mistakes

Using server_name instead of listen for port.

The listen directive tells Nginx which port to listen on for incoming requests. Port 80 is the default for HTTP.

3fill in blank

hard

Fix the error in the server block to serve multiple domains.

Nginx

server {
    listen 80;
    server_name example.com [1];
    root /var/www/example;
}

Drag options to blanks, or click blank then click option'

Alocation

Blisten

Croot

Dexample.org

Attempts:

3 left

💡 Hint

Common Mistakes

Adding directives instead of domain names in server_name.

To serve multiple domains in one server block, list them all in the server_name directive separated by spaces.

4fill in blank

hard

Fill both blanks to configure two server blocks for different domains.

Nginx

server {
    listen 80;
    server_name [1];
    root /var/www/site1;
}

server {
    listen 80;
    server_name [2];
    root /var/www/site2;
}

Drag options to blanks, or click blank then click option'

Asite1.com

Bsite2.com

Cexample.com

Dlocalhost

Attempts:

3 left

💡 Hint

Common Mistakes

Using the same domain for both server blocks.

Each server block should have its own domain in server_name to serve different sites.

5fill in blank

hard

Fill all three blanks to complete the virtual host configuration for multiple domains with different roots.

Nginx

server {
    listen [1];
    server_name [2];
    root [3];
}

Drag options to blanks, or click blank then click option'

A80

Bmydomain.com

C/var/www/mydomain

D443

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 443 without SSL configuration.

Setting root to wrong directory.

Listen on port 80 for HTTP, set the server_name to the domain, and root to the folder with site files.

Practice

1. What is the main purpose of virtual hosting in nginx?

easy

A. To create backups of website data automatically

B. To increase the server's CPU speed

C. To block unwanted visitors from accessing the server

D. To serve multiple websites from a single server using different domain names

Solution

1. Step 1: Understand virtual hosting concept

   Virtual hosting allows one server to handle many websites by using domain names to select content.

2. Step 2: Identify the main purpose

   This means the server can serve different websites without needing separate servers for each domain.

3. Final Answer:

   To serve multiple websites from a single server using different domain names -> Option D

4. Quick Check:

   Virtual hosting = multiple domains on one server [OK]

Hint: Virtual hosting means many sites, one server [OK]

Common Mistakes:

• Thinking virtual hosting speeds up CPU
• Confusing virtual hosting with backups
• Believing it blocks visitors

2. Which nginx directive is used to specify the domain names for virtual hosting?

easy

A. server_name

B. location

C. listen

D. root

Solution

1. Step 1: Recall nginx configuration directives

   The server_name directive tells nginx which domain names a server block should respond to.

2. Step 2: Match directive to purpose

   Other directives like root set content folder, listen sets port, location defines URL paths.

3. Final Answer:

   server_name -> Option A

4. Quick Check:

   Domain names use server_name [OK]

Hint: Domain names go in server_name directive [OK]

Common Mistakes:

• Using root for domain names
• Confusing listen with domain matching
• Thinking location sets domain

3. Given this nginx server block snippet, what domain will it serve?

server {
  listen 80;
  server_name example.com www.example.com;
  root /var/www/example;
}

medium

A. Only example.com

B. Only www.example.com

C. Both example.com and www.example.com

D. Any domain on port 80

Solution

1. Step 1: Read server_name directive

   The server_name lists both example.com and www.example.com, so nginx matches requests for either domain.

2. Step 2: Understand nginx matching

   Requests to either domain on port 80 will serve content from /var/www/example.

3. Final Answer:

   Both example.com and www.example.com -> Option C

4. Quick Check:

   server_name lists multiple domains = serve all listed [OK]

Hint: server_name can list many domains separated by spaces [OK]

Common Mistakes:

• Assuming only first domain is served
• Thinking root defines domain
• Believing nginx serves all domains by default

4. You configured two server blocks with the same server_name but different root paths. What will happen when a request comes for that domain?

medium

A. nginx will merge both roots and serve combined content

B. nginx will serve content from the first server block it finds

C. nginx will return an error about duplicate server_name

D. nginx will randomly choose one root each time

Solution

1. Step 1: Understand nginx server block matching

   When multiple server blocks have the same server_name, nginx uses the first matching block it finds in the config.

2. Step 2: Result of duplicate server_name

   It does not merge roots or error out; it simply picks the first block, so only one root is used.

3. Final Answer:

   nginx will serve content from the first server block it finds -> Option B

4. Quick Check:

   Duplicate server_name = first block wins [OK]

Hint: Duplicate server_name uses first matching block [OK]

Common Mistakes:

• Expecting nginx to merge content folders
• Thinking nginx throws error on duplicates
• Assuming random selection

5. You want to serve two domains, site1.com and site2.com, on the same nginx server. Which configuration correctly uses virtual hosting to serve different content for each domain?

hard

A. server { listen 80; server_name site1.com; root /var/www/site1; } server { listen 80; server_name site2.com; root /var/www/site2; }

B. server { listen 80; server_name site1.com site2.com; root /var/www/site1; }

C. server { listen 80; server_name site1.com; root /var/www/site1; } server { listen 80; server_name site1.com; root /var/www/site2; }

D. server { listen 80; root /var/www/site1; } server { listen 80; root /var/www/site2; }

Solution

1. Step 1: Check domain to root mapping

   server { listen 80; server_name site1.com; root /var/www/site1; } server { listen 80; server_name site2.com; root /var/www/site2; } uses two server blocks, each with a unique server_name and root folder, correctly separating content by domain.

2. Step 2: Analyze other options

   server { listen 80; server_name site1.com site2.com; root /var/www/site1; } serves both domains from one root, so content is not separated. server { listen 80; server_name site1.com; root /var/www/site1; } server { listen 80; server_name site1.com; root /var/www/site2; } duplicates server_name causing conflict. server { listen 80; root /var/www/site1; } server { listen 80; root /var/www/site2; } lacks server_name, so domains won't be matched properly.

3. Final Answer:

   Two server blocks with distinct server_name and root for each domain -> Option A

4. Quick Check:

   Separate server blocks = separate domains and content [OK]

Hint: Use separate server blocks for each domain with server_name [OK]

Common Mistakes:

• Putting multiple domains in one block with one root
• Duplicating server_name in multiple blocks
• Omitting server_name directive