How to setup nameservers with BIND? CentOS Web Panel

Quick and easy info how to setup your own nameservers with CentOS Web Panel Server using BIND DNS Server.

CENTOS WEB PANEL – SYSTEM REQUIREMENTS

Make sure that you complete the following tasks before you start the installation process:

1. Setup Hostname

This hostname cannot be the same as any domain that is on your server (for example, if example.com is a domain on your server, use hostname.example.com as your fully qualified hostname).

You can use the following command for hostname setup eg. srv1.example.com

hostname srv1.example.com

2. Setup Server IP addresses

• Define additional IP address, subnet address, and default gateway IP address for your server — your service provider can provide you with this information.

3. Software Requirements

• You must have a clean/fresh installation of supported operating systems:
• CentOS 6, RedHat 6 or CloudLinux 6, MINIMAL installation and English version only!
• CentOS 7 is NOT supported.

4. Hardware Requirements

• 32 bit operating systems require a minimum of 512 MB RAM
• 64 bit operating systems require a minimum of 1024 MB RAM (recommended)
• Recommended System: 4 GB+ RAM so you would have the full functionality such as Anti-virus scan of emails.

Host Multiple Domains on One Server/IP with Apache or nginx

Configure Apache/Nginx to host multiple websites

If you are on dedicated or VPS like DigitalOcean or any other server and planning to host multiple websites on a single server then here is how you can do it either with Apache HTTP or Nginx web server.

This assumes you have already mapped DNS to your host, like following two domains I have mapped to DigitalOcean.

1. bestflare.com
2. usefulread.com

Before you implement this, to give you an idea how it works. The concept to have multiple websites on a single instance is called Virtual Server. Virtual server configuration is defined within web server configuration and based on server/IP address, a request is getting forwarded to respective Document Root.

Configure Virtual Host in Apache to host multiple domains

• Login into Apache HTTP Server
• Go to apache conf location. ( in default installation – you will find it here /etc/httpd/conf/httpd.conf)
• Take a backup of httpd.conf file
• Create a VirtualHost container like below I have done for two domains.

<VirtualHost *:80>
ServerAdmin hello@chandank.com
   DocumentRoot /opt/htdocs/bestflare
   ServerName bestflare.com
   ErrorLog logs/bestflare.com-error_log
   CustomLog logs/bestflare.com-access_log common
</VirtualHost>
<VirtualHost *:80>
   ServerAdmin hello@chandank.com
   DocumentRoot /opt/htdocs/usefulread
   ServerName usefulread.com
   ErrorLog logs/usefulread.com-error_log
   CustomLog logs/usefulread.com-access_log common
</VirtualHost>

Note: Change the value for ServerAdmin, DocumentRoot, ServerName, ErrorLog, CustomLog based on your requirement.

• Restart Apache HTTP and test both urls.

Configure Virtual Host in Nginx to host multiple domains

• Login into Nginx server
• Go to virtual.conf location (in default location – you will find it here /etc/nginx/conf.d/virtual.conf)
• Take a backup of virtual.conf
• Create server block for both URL’s as I have shown below.

server {
listen 80;
   root /opt/htdocs/bestflare;
index index.html index.htm;
   server_name bestflare.com;
   location / {
       try_files $uri $uri/ =404;
   }
}
server {
   listen 80;
   root /opt/htdocs/usefulread;
   index index.html index.htm;
   server_name usefulread.com;
   location / {
       try_files $uri $uri/ =404;
   }
}

Note: Change the value for root, server_name based on your requirement.

• Restart Nginx and test both URL’s

Why We Love OpenCart

1. OpenCart is Free

2. Open-Source, Customizable and Flexible

3. Responsive Design

4. Free and Paid Functionality Extensions

5. SEO Ready

6. Analytics, Statistics and Advanced Data Tracking

7. Secure Payment and Shipping Methods

8. Multi-Store and Multi-Lingual Capabilities

9. Coupons, Specials, Reward Points and Gift Vouchers

10. Large User Base and Community

How to install Softaculous with CentOS Web Panel

How TO Setup Remote Backup CWP

ssh remote key authentication

Instructions for adding ssh pub key on the remote backup server.
Replace the USERNAME with the existing username on the remote server, it’s not recommended to use the root user.

This instructions are only for the backups on the remote server.
To Enable remote backup in your CWP.admin go to CWP Settings –> Backup Configuration

You will need to enter the login details into the fields of “Remote Backup Settings”
Don’t forget to generate the new remote access Key.

On the remote backup server you need to add the pub key
cd ~USERNAME
mkdir .ssh
chmod 700 .ssh
nano .ssh/authorized_keys
Now add all content from the file /root/.ssh/backup/id_rsa.pub to .ssh/authorized_keys
chmod 600 .ssh/authorized_keys
chown -R USERNAME:USERNAME .ssh
chown USERNAME:USERNAME .ssh/authorized_keys

You can use test connection button in CWP.admin to check connectivity with the remote backup server.

To connect and check content on the backup server you can use ssh key access:

ssh USERNAME@SERVER-IP -i /root/.ssh/backup/id_rsa

vQmod Scripts and Syntax

Scripting

The Golden Rules

First things to set in your mind...

• The <search> tag can only be a single line, though doesn't have to be a whole line, as partial matches work too. You should learn how to use the offset attribute to properly encompass all needed lines, but that doesn't mean you should encompass many lines. Instead of trying to include many lines from top down, try starting at the bottom and finding lines going up.
• Less is more! Whenever possible, try to match the smallest, yet still unique part of the code. That will improve the chances of being more future-resistant and avoid breaking other mods that may have changes close to yours.
• Pay attention to all the attribute options for each tag. There is a lot of power that is overlooked by people skimming over the syntax

How to make vQmod Scripts

vQmod currently uses an xml formatted parser by default but other parsers can be created in the future as well.

A simple replace script example looks like this:

    <?xml version="1.0" encoding="UTF-8"?>
    <modification
                xmlns="https://github.com/vqmod/vqmod"
                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                xsi:schemaLocation="https://github.com/vqmod/vqmod https://raw.githubusercontent.com/vqmod/vqmod/master/vqmod.xsd"
                >
        <id>Replace 123 with ABC</id>
        <version>1.0.0</version>
        <vqmver>2.5.0</vqmver>
        <author>qphoria</author>

        <file name="relative/path/myfile.php">
            <operation>
                <search position="replace"><![CDATA[
                $var = '123';
                ]]></search>

                <add><![CDATA[
                $var = 'ABC';
                ]]></add>
            </operation>
        </file> 
    </modification>

This script simply changes the value of a variable of "myfile.php" from "123" to "ABC" before it gets included.

Syntax

vQmod supports a number of parameters:

modification

• This is the highest level of the file and there can only be one

modification / id

• This is the name and description of the mod.
• Format: Free form text. (Informational)

modification / version

• This is the version of the mod.
• Format: Number and Decimal (1.0.0) (Informational)

modification / vqmver

• This is the minimum required version of VirtualQMod needed for the script to work.
• Format: Number and Decimal (1.0.0) (Informational)
• A required="true" attribute can be optionally set to disable the script if it doesn't meet the required version (Added from 2.4.0)

modification / author

• This is the author of the mod.
• Format: Free form text (Informational)

modification / file

• This is the name of the file to modify
• Requires attribute "name" as relative filename to the location of the main index.php file (e.g. catalog/controller/product/product.php). Can be delimited with commas to apply to multiple files at once (2.3.0 +) Name attribute supports a wildcard (*) character for dynamic path building. Each wildcard is limited to a single directory level.

     - catalog/view/theme/*/template/product/product.tpl
     - catalog/view/theme/*/*/product/product.tpl
     - etc

• There can be multiple file tags in a single xml file. Each file can have its own set of operations
• Optional attribute "path" can be used to prefix file name's to avoid repetition. This is simply prepended to the file names and no validation is attempted (2.3.0 +)
• Optional attribute "error" set to log|skip|abort
  • skip means it will simply ignore this file.
  • log is the same as skip, but logs the error. (default)
  • abort means to log the error and cancel the remaining operations in that particular xml script. It does not revert changes to other files already made in that script and doesn't stop other xml files.
  • Wildcard paths will ignore the "error" attribute completely

modification / file / operation

• This is the wrapper of the actual operation occurring.
• There can be multiple operations to the same file tag.
• Optional attribute "info" suggested. May be used by vQmod/vQmod Manager for OC in the future but at present isn't used. This is however ideal for making files easier to read
• Optional attribute "error" set to skip|log|abort
  • skip means all other operations will be applied even if one cannot. There will be no error in the log.
  • log is the same as skip, but logs the error.
  • abort means to log the error and revert to the original source. (default)

modification / file / operation / ignoreif

• This allows for a search to be made on a file. This search works across multiple lines not just single lines. This tag is optional and if the search is found, the operation is skipped
  • Optional attribute "regex' set to true|false. Format of data inside tag then requires delimiters for regex as it uses the standard preg_match method for php. This attribute defaults to false

modification / file / operation / search

• This is the first required step of the operation.
• Can only search single lines, both fully and partially. But offset and index attributes will assist.
• Automatically trims whitespace and linebreaks
• One <search> tag per <operation> tag
• Use CDATA tags to wrap code.
• Required attribute "position" set to before|after|replace|top|bottom|all|ibefore|iafter.
  • replace will replace the data in the search tag with the data in the add tag. (default)
  • before will insert the add data before the search data
  • after will insert the add data after the search data
  • top will insert the add data at the top of the file. The search data is ignored.
  • bottom will insert the add data at the bottom of the file. The search data is ignored.
  • all will completely replace all the code in the file with the add data. The search data is ignored. Deprecated as of 2.4.0
  • ibefore will insert the code before the search inline instead of the line before
  • iafter will insert the code afterthe search inline instead of the line before
• Optional attribute "offset" to work with the position
  • if the search position is before and offset 3 it will put the add data before the line, 3 lines above the searched line
  • if the search position is after and offset 3 it will put the add data after the line, 3 lines below the searched line
  • if the search position is replace and offset 3 it will remove the code from the search line and the next 3 lines and replace it with the add data
  • if the search position is top and offset 3 it will put the code before the line, 3 lines below the top of the file
  • if the search position is bottom and offset 3 it will put the code after the line, 3 lines above the bottom of the file
• Optional attribute "index" for specifying which instances of a search tag should be acted on
  • If the search string is "echo" and there are 5 echos in the file, but only want to replace the 1st and 3rd, use index="1,3"
  • Comma delimited for multiple instances starting with "1"
  • Leave out or set to FALSE to replace all instances. (default)
• Optional attribute "regex" for specifying whether or not to search a regex pattern.
  • If true, the search data should be a valid regex pattern
  • Leave out or set to FALSE to use normal string search (default)
  • Does not apply to ibefore and iafter
• Optional attribute "trim" set to true|false
  • true will trim away whitespace and linebreaks.
  • leave out or set to true to trim. (default is true)

modification / file / operation / add

• This is the second required step of the operation.
• Can be multiple lines
• One <add> tag per <operation> tag.
• Location of added data depends on the position attribute of the search command.
• Use CDATA tags to wrap code.
• NEW IN 2.6.0: <add> tag now supports all the search attributes.
• Attributes in the <add> tag will override attributes in the <search> tag.
• Optional attribute "position" set to before|after|replace|top|bottom|ibefore|iafter.
  • replace will replace the data in the search tag with the data in the add tag. (default)
  • before will insert the add data before the search data
  • after will insert the add data after the search data
  • top will insert the add data at the top of the file. The search data is ignored.
  • bottom will insert the add data at the bottom of the file. The search data is ignored.
  • ibefore will insert the code before the search inline instead of the line before
  • iafter will insert the code afterthe search inline instead of the line before
• Optional attribute "offset" to work with the position
  • if the search position is before and offset 3 it will put the add data before the line, 3 lines above the searched line
  • if the search position is after and offset 3 it will put the add data after the line, 3 lines below the searched line
  • if the search position is replace and offset 3 it will remove the code from the search line and the next 3 lines and replace it with the add data
  • if the search position is top and offset 3 it will put the code before the line, 3 lines below the top of the file
  • if the search position is bottom and offset 3 it will put the code after the line, 3 lines above the bottom of the file
• Optional attribute "index" for specifying which instances of a search tag should be acted on
  • If the search string is "echo" and there are 5 echos in the file, but only want to replace the 1st and 3rd, use index="1,3"
  • Comma delimited for multiple instances starting with "1"
  • Leave out or set to FALSE to replace all instances. (default)
• Optional attribute "regex" for specifying whether or not to search a regex pattern.
  • If true, the search data should be a valid regex pattern
  • Leave out or set to FALSE to use normal string search (default)
  • Does not apply to ibefore and iafter
• Optional attribute "trim" set to true|false
  • true will trim away whitespace and linebreaks.
  • leave out or set to true to trim. (default is true)

<![CDATA[ ]]>

• These are called CDATA tags and they are used by xml to specify that the data between should not be evaluated. It's recommended you always use these for data between the and operation tags