Two Subdomains on Same Public IP but Two Different Webservers

When it comes to hosting websites, there are various ways to configure your server to handle multiple domains and subdomains. One common scenario is having two subdomains on the same public IP address but with two different webservers. In this article, we will explore how this setup works and the steps to implement it.

Understanding Subdomains

Before we dive into the technical details, let's first understand what subdomains are. A subdomain is a part of a larger domain name. For example, in the domain name "example.com," the subdomain could be "blog.example.com" or "shop.example.com." Each subdomain can be treated as a separate website with its own unique content and functionality.

Why Use Two Different Webservers?

There are several reasons why you might want to use two different webservers for your subdomains:

• Separation of Services: By using different webservers, you can separate the functionality and resources of each subdomain. This can be useful when you want to have different technologies or configurations for each subdomain.
• Load Balancing: If you expect high traffic on your subdomains, using two different webservers can help distribute the load and improve performance.
• Redundancy: Having multiple webservers ensures that if one server goes down, the other can still handle requests, providing a higher level of availability.

Configuring Two Subdomains on the Same Public IP

To configure two subdomains on the same public IP address with different webservers, you need to follow these steps:

Step 1: Set Up DNS Records

The first step is to configure the DNS records for your subdomains. DNS (Domain Name System) is responsible for translating domain names into IP addresses. You need to create two separate DNS records, each pointing to the same public IP address.

For example, let's say you have two subdomains: "sub1.example.com" and "sub2.example.com." You would create two DNS records like this:

Make sure to replace "Your_Public_IP_Address" with the actual IP address of your server.

Step 2: Configure Port Forwarding

Next, you need to configure port forwarding on your router or firewall to redirect incoming traffic to the appropriate webservers. Port forwarding allows you to specify which ports should be directed to which internal IP addresses.

In this case, you will need to forward port 80 (HTTP) and port 443 (HTTPS) to the internal IP addresses of your webservers.

Step 3: Set Up Webserver 1

Now, let's configure the first webserver for "sub1.example.com." This could be Apache, Nginx, or any other webserver software.

Here are the basic steps to set up Webserver 1:

1. Install the webserver software on your server.
2. Create a new virtual host configuration for "sub1.example.com."
3. Specify the document root directory where the files for "sub1.example.com" will be stored.
4. Configure any necessary settings and permissions for the webserver.
5. Test the configuration and make sure "sub1.example.com" is accessible.

Step 4: Set Up Webserver 2

Similarly, you will now configure the second webserver for "sub2.example.com."

Follow these steps to set up Webserver 2:

1. Install the webserver software on your server.
2. Create a new virtual host configuration for "sub2.example.com."
3. Specify the document root directory where the files for "sub2.example.com" will be stored.
4. Configure any necessary settings and permissions for the webserver.
5. Test the configuration and make sure "sub2.example.com" is accessible.

Step 5: Test the Setup

Once you have set up both webservers, it's time to test the configuration. Open a web browser and try accessing "sub1.example.com" and "sub2.example.com." Each subdomain should display the content served by its respective webserver.

Conclusion

Congratulations! You have successfully configured two subdomains on the same public IP address with two different webservers. This setup allows you to separate services, balance the load, and improve redundancy for your websites. By following the steps outlined in this article, you can easily implement this configuration on your own server.

References