{"id":11713,"date":"2019-03-15T23:26:11","date_gmt":"2019-03-15T23:26:11","guid":{"rendered":"http:\/\/www.appservgrid.com\/paw92\/?p=11713"},"modified":"2019-03-15T23:26:11","modified_gmt":"2019-03-15T23:26:11","slug":"apache-virtual-hosting-ip-based-and-name-based-virtual-hosts-in-rhel-centos-fedora","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw92\/index.php\/2019\/03\/15\/apache-virtual-hosting-ip-based-and-name-based-virtual-hosts-in-rhel-centos-fedora\/","title":{"rendered":"Apache Virtual Hosting: IP Based and Name Based Virtual Hosts in RHEL\/CentOS\/Fedora"},"content":{"rendered":"

As we all are aware that\u00a0Apache<\/strong>\u00a0is a very powerful, highly flexible and configurable Web server for\u00a0Nix OS<\/strong>. Here in this tutorial, we are going to discuss one more feature of\u00a0Apache<\/strong>\u00a0which allows us to host more than one website on a single Linux machine. Implementing virtual hosting with Apache web server can help you to save costs you are investing on your server maintenance and their administration.<\/p>\n

Don\u2019t Miss<\/b>:\u00a0NGINX Name-based and IP-based Virtual Hosting (Server Blocks)<\/a><\/p>\n

\n

\"Apache<\/a><\/p>\n

Apache Virtual Hosting in Linux<\/p>\n<\/div>\n

Concept of\u00a0Shared web hosting<\/strong>\u00a0and\u00a0Reseller web hosting<\/strong>\u00a0is based on this facility of\u00a0Apache<\/strong>\u00a0only.<\/p>\n

Types of Virtual Host<\/h4>\n

There are two types of virtual hosting is available with Apache.<\/p>\n

Name Based Virtual Hosting<\/h5>\n

With the name based virtual hosting you can host several\u00a0domains<\/strong>\/websites<\/strong>\u00a0on a single machine with a singleIP<\/strong>. All domains on that server will be sharing a single IP. It\u2019s easier to configure than IP based virtual hosting, you only need to configure\u00a0DNS<\/strong>\u00a0of the domain to map it with its correct IP address and then configure Apache to recognize it with the domain names.<\/p>\n

\n

\"Name<\/a><\/p>\n

Name Based Virtual Hosting<\/p>\n<\/div>\n

IP Based Virtual Hosting<\/h5>\n

With the IP based virtual hosting, you can assign a separate IP for each domain on a single server, these IP\u2019s can be attached to the server with single NIC cards and as well as multiple NICs.<\/center><\/p>\n
\n

\"IP<\/a><\/p>\n

IP Based Virtual Hosting<\/p>\n<\/div>\n

Lets set up\u00a0Name Based Virtual Hosting<\/strong>\u00a0and\u00a0IP based Virtual hosting<\/strong>\u00a0in\u00a0RHEL, CentOS<\/strong>\u00a0and\u00a0Fedora<\/strong>.<\/p>\n

Testing Environment<\/h5>\n
    \n
  1. OS<\/strong>\u00a0\u2013\u00a0CentOS 6.5<\/strong><\/li>\n
  2. Application<\/strong>\u00a0\u2013\u00a0Apache Web Server<\/strong><\/li>\n
  3. IP Address<\/strong>\u00a0\u2013\u00a0192.168.0.100<\/strong><\/li>\n
  4. IP Address<\/strong>\u00a0\u2013\u00a0192.168.0.101<\/strong><\/li>\n
  5. Domain<\/strong>\u00a0\u2013\u00a0www.example1.com<\/strong><\/li>\n
  6. Domain<\/strong>\u00a0\u2013\u00a0www.example2.com<\/strong><\/li>\n<\/ol>\n

    How to Setup IP Based and Name Based Apache Virtual Hosts<\/h3>\n

    Before setting up virtual hosting with\u00a0Apache<\/strong>, your system must have Apache Web software installed. if not, install it using default package installer called yum.<\/p>\n

    [root@tecmint ~]# yum install httpd<\/pre>\n
    Setup Name Based Virtual Host<\/h4>\n
    But, before creating a virtual host, you need to create a directory where you will keep all your website\u2019s files. So, create directories for these two virtual hosts under\u00a0\/var\/www\/html<\/strong>\u00a0folder. Please remember\u00a0\/var\/www\/html<\/strong>\u00a0will be your default\u00a0Document Root<\/strong>\u00a0in the Apache virtual configuration.<\/p>\n
    [root@tecmint ~]# mkdir \/var\/www\/html\/example1.com\/\r\n[root@tecmint ~]# mkdir \/var\/www\/html\/example2.com\/<\/pre>\n
    To set up Name based virtual hosting you must need to tell Apache to which IP you will be using to receive the Apache requests for all the websites or domain names. We can do this with\u00a0NameVirtualHost<\/strong>\u00a0directive. Open Apache main configuration file with\u00a0VI<\/strong>\u00a0editor.<\/p>\n
    [root@tecmint ~]# vi \/etc\/httpd\/conf\/httpd.conf<\/pre>\n
    Search for\u00a0NameVirtualHost<\/strong>\u00a0and uncomment this line by removing the\u00a0#<\/strong>\u00a0sign in front of it.<\/p>\n
    NameVirtualHost<\/pre>\n
    Next add the IP with possible in which you want to receive Apache requests. After the changes, your file should look like this:<\/p>\n
    NameVirtualHost 192.168.0.100:80<\/pre>\n
    Now, it\u2019s time to setup Virtual host sections for your domains, move to the bottom of the file by pressing\u00a0Shift + G<\/strong>. Here in this example, We are setting up virtual host sections for two domains<\/p>\n
      \n
    1. www.example1.com<\/strong><\/li>\n
    2. www.example2.com<\/strong><\/li>\n<\/ol>\n
      Add the following two virtual directives at the bottom of the file. Save and close the file.<\/p>\n
      <VirtualHost 192.168.0.100:80>\r\n    ServerAdmin webmaster@example1.com\r\n    DocumentRoot \/var\/www\/html\/example1.com\r\n    ServerName www.example1.com\r\nErrorLog logs\/www.example1.com-error_log\r\nCustomLog logs\/www.example1.com-access_log common\r\n<\/VirtualHost>\r\n\r\n<VirtualHost *:80>\r\n    ServerAdmin webmaster@example2.com\r\n    DocumentRoot \/var\/www\/html\/example2.com\r\n    ServerName www.example2.com\r\nErrorLog logs\/www.example2.com-error_log\r\nCustomLog logs\/www.example2.com-access_log common\r\n<\/VirtualHost><\/pre>\n
      You are free to add as many directives you want to add in your domains virtual host section. When you are done with changes in\u00a0httpd.conf<\/strong>\u00a0file, please check the syntax of files with following command.<\/p>\n
      [root@tecmint ~]# httpd -t\r\n\r\nSyntax OK<\/pre>\n
      It is recommended to check the syntax of the file after making some changes and before restarting the Web server because if any syntax goes wrong Apache will refuse to work with some errors and eventually affect your existing web server go down for a while. If syntax is\u00a0OK<\/strong>. Please restart your Web server and add it to\u00a0chkconfig<\/strong>to make your web server start in\u00a0runlevel 3<\/strong>\u00a0and\u00a05<\/strong>\u00a0at the boot time only.<\/p>\n
      [root@tecmint ~]# service httpd restart\r\nStopping httpd:                                            [  OK  ]\r\nStarting httpd:                                            [  OK  ]<\/pre>\n
      [root@tecmint ~]# chkconfig --level 35 httpd on<\/pre>\n
      Now it\u2019s time to create a test page called\u00a0index.html<\/strong>\u00a0add some content to the file so we will have something to check it, when the IP calls the virtual host.<\/p>\n
      [root@tecmint ~]# vi \/var\/www\/html\/example1.com\/index.html<\/pre>\n
      <html>\r\n  <head>\r\n    <title>www.example1.com<\/title>\r\n  <\/head>\r\n  <body>\r\n    <h1>Hello, Welcome to www.example1.com.<\/h1>\r\n  <\/body>\r\n<\/html><\/pre>\n
      [root@tecmint ~]# vi \/var\/www\/html\/example2.com\/index.html<\/pre>\n
      <html>\r\n  <head>\r\n    <title>www.example2.com<\/title>\r\n  <\/head>\r\n  <body>\r\n    <h1>Hello, Welcome to www.example2.com.<\/h1>\r\n  <\/body>\r\n<\/html><\/pre>\n
      Once you\u2019re done with it, you can test the setup by accessing both the domains in a browser.<\/p>\n
      http:\/\/www.example1.com\r\nhttp:\/\/www.example2.com<\/pre>\n
      Preview: www.example1.com<\/h5>\n
      \n
      \"Virtual<\/a><\/p>\n
      Virtual Hosting: www.example1.com<\/p>\n<\/div>\n
      Preview: www.example2.com<\/h5>\n
      \n
      \"Virtual<\/a><\/p>\n
      Virtual Hosting: www.example2.com<\/p>\n<\/div>\n
      Setup IP Based Virtual Hosting Linux<\/h4>\n
      To setup IP based virtual hosting, you must have more than one\u00a0IP address<\/strong>\/Port<\/strong>\u00a0assigned to your server or your Linux machine.<\/p>\n
      It can be on a single\u00a0NIC<\/strong>\u00a0card , For example:\u00a0eth0:1<\/strong>,\u00a0eth0:2<\/strong>,\u00a0eth0:3<\/strong>\u00a0\u2026 so forth. Multiple\u00a0NIC<\/strong>\u00a0cards can also be attached. If you don\u2019t know how to create multiple IP\u2019s on single\u00a0NIC<\/strong>, follow the below guide, that will help you out in creating.<\/p>\n
        \n
      1. Create Multiple IP Addresses to One Single Network Interface<\/a><\/li>\n<\/ol>\n
        Purpose of implementing\u00a0IP based virtual hosting<\/strong>\u00a0is to assign implementing for each domain and that particular IP will not be used by any other domain.<\/p>\n
        This kind of set up required when a website is running with\u00a0SSL<\/strong>\u00a0certificate (mod_ssl<\/strong>) or on different ports and IPs. And You can also run multiple instances of Apache on a single machine. To check the IPs attached in your server, please check it using\u00a0ifconfig command<\/a>.<\/p>\n
        root@tecmint ~]# ifconfig<\/pre>\n
        Sample Output<\/h5>\n
         \r\neth0      Link encap:Ethernet  HWaddr 08:00:27:4C:EB:CE  \r\n          inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0\r\n          inet6 addr: fe80::a00:27ff:fe4c:ebce\/64 Scope:Link\r\n          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1\r\n          RX packets:17550 errors:0 dropped:0 overruns:0 frame:0\r\n          TX packets:15120 errors:0 dropped:0 overruns:0 carrier:0\r\n          collisions:0 txqueuelen:1000\r\n          RX bytes:16565983 (15.7 MiB)  TX bytes:2409604 (2.2 MiB)\r\n\r\neth0:1    Link encap:Ethernet  HWaddr 08:00:27:4C:EB:CE  \r\n          inet addr:192.168.0.101  Bcast:192.168.0.255  Mask:255.255.255.0\r\n          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1\r\n\r\nlo        Link encap:Local Loopback  \r\n          inet addr:127.0.0.1  Mask:255.0.0.0\r\n          inet6 addr: ::1\/128 Scope:Host\r\n          UP LOOPBACK RUNNING  MTU:16436  Metric:1\r\n          RX packets:1775 errors:0 dropped:0 overruns:0 frame:0\r\n          TX packets:1775 errors:0 dropped:0 overruns:0 carrier:0\r\n          collisions:0 txqueuelen:0\r\n          RX bytes:3416104 (3.2 MiB)  TX bytes:3416104 (3.2 MiB)<\/pre>\n
        As you can see in above output, two IPs\u00a0192.168.0.100<\/strong>\u00a0(eth0<\/strong>) and\u00a0192.168.0.101<\/strong>\u00a0(eth0:1<\/strong>) is attached to the server, both IPs are assigned to the same physical network device (eth0<\/strong>).<\/p>\n
        Now, assign a specific\u00a0IP<\/strong>\/Port<\/strong>\u00a0to receive http requests, you can simply do it by changing\u00a0Listen<\/strong>\u00a0directive in\u00a0httpd.conf<\/strong>\u00a0file.<\/p>\n
        [root@tecmint ~]# vi \/etc\/httpd\/conf\/httpd.conf<\/pre>\n
        Search for word \u201cListen<\/strong>\u201d, You find a section where the short description about Listen directive is written. In that section, comment the original line and write your own directive below that line.<\/p>\n
        # Listen 80\r\n\r\nListen 192.168.0.100:80<\/pre>\n
        Now,\u00a0 create a Virtual host sections for both the domains. Go the bottom of the file and add the following virtual directives.<\/p>\n
        <VirtualHost 192.168.0.100:80>\r\n    ServerAdmin webmaster@example1.com\r\n    DocumentRoot \/var\/www\/html\/example1\r\n    ServerName www.example1.com\r\nErrorLog logs\/www.example1.com-error_log\r\nTransferLog logs\/www.example1.com-access_log\r\n<\/VirtualHost>\r\n\r\n<VirtualHost 192.168.0.101:80>\r\n    ServerAdmin webmaster@example2.com\r\n    DocumentRoot \/var\/www\/html\/example2\r\n    ServerName www.example2.com\r\nErrorLog logs\/www.example2.com-error_log\r\nTransferLog logs\/www.example2.com-access_log\r\n<\/VirtualHost><\/pre>\n
        Now, since you have modified main Apache conf file, you need to restart the http service like below.<\/p>\n
        [root@tecmint ~]# service httpd restart\r\nStopping httpd:                                            [  OK  ]\r\nStarting httpd:                                            [  OK  ]<\/pre>\n
        Test your IP based Virtual hosting setup by accessing the\u00a0URLs<\/strong>\u00a0on web browser as shown below.<\/p>\n
        http:\/\/www.example1.com\r\nhttp:\/\/www.example2.com<\/pre>\n
        That\u2019s all with Apache virtual host today, If you\u2019re looking to secure and harden your Apache configuration, then read our article that guides.<\/p>\n
          \n
        1. 13 Apache Web Server Security and Hardening Tips<\/a><\/li>\n<\/ol>\n
          Reference Links<\/h3>\n
          Apache Virtual Host Documentation<\/a><\/p>\n
          I\u2019ll be again come with some other Apache tips and trick in my future articles, till then Stay Geeky and connected to Tecmint.com. Do not forget to leave your suggestions about the article in our comment section below.<\/p>\n
          Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
          As we all are aware that\u00a0Apache\u00a0is a very powerful, highly flexible and configurable Web server for\u00a0Nix OS. Here in this tutorial, we are going to discuss one more feature of\u00a0Apache\u00a0which allows us to host more than one website on a single Linux machine. Implementing virtual hosting with Apache web server can help you to save … <\/p>\n
          Continue reading “Apache Virtual Hosting: IP Based and Name Based Virtual Hosts in RHEL\/CentOS\/Fedora”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-11713","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/11713","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/comments?post=11713"}],"version-history":[{"count":1,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/11713\/revisions"}],"predecessor-version":[{"id":11714,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/11713\/revisions\/11714"}],"wp:attachment":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/media?parent=11713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/categories?post=11713"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/tags?post=11713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}