How to import sites with custom MX records Ensim Pro Control Panel Linux
The import of a site with custom MX records could cause creation of duplicated MX records: apart from custom MX records which are defined in the imported archive, default MX records could be created.
In order to avoid this, please proceed through the following steps when importing a site with custom MX records:
1. Before importing sites disable the creation of default MX records. Run the following command(s) as root:
/usr/local/bin/SetDefaultMXRecordState -f on
2. Restart epld service using the following commands as root:
3. Import site from the archive.
4. When the site is succesfuly imported, please turn off the freezing of MX records for imported sites.
For this, run the following commands as root:
/usr/local/bin/SetDefaultMXRecordState -f off
Reference : http://parallels.com/
Try removing –with-openssl from your configure.php file and recompile php.
cd /usr/local/directadmin/customapache
vi configure.php
#remove –with-openssl from the file, save, exit.
./build clean
./build php n
DirectAdmin custom httpd.conf code to the VirtualHosts of a domain
DirectAdmin Allows Admin to insert extra httpd.conf code that a User may require. To access the control page for this functionality, go to Admin Panel -> Admin Settings -> Customize Httpd Configurations.
Once you see the list of domain, click the domain you wish to insert the extra httpd.conf code to.
Another common use is to add another ServerAlias. This allows another domain to be used to access the exact same content. To accomplish this, you would write
ServerAlias mynew-domain.com www.mynew-domain.com
To get mynew-domain.com and www.mynew-domain.com to point to the original domain for the VirtualHost. You will also have to make sure that mynew-domain.com and www.mynew-domain.com both resolve to the same IP.
Using a custom VirtualHost template in DirectAdmin
If you wish to change the setup of the VirtualHosts for all domains, you can do so by creating your own custom templates.
cd /usr/local/directadmin/data/templates
cp virtual_host*.conf custom
cd custom
Once you’ve copied the 4 VirtualHost files (or just the ones you want) to the custom directory, you can then edit the new files you’ve just copied. DirectAdmin will always check for the custom file before going to the default ones. Failure to copy the virtual_host*.conf files to the custom directory before modifying them will result in a loss of all changes when DirectAdmin updates itself (the files are overwritten).
Once you are happy with your new virtual_host*.conf files they’ll need to be used in the real httpd.conf files. You can trigger DirectAdmin to rewrite all User httpd.conf files by running:
echo “action=rewrite&value=httpd” >> /usr/local/directadmin/data/task.queue
The command will be added the the task queue which is checked once per minute, so it may be a few minutes before all httpd.conf files have been rewritten. *Note: the main /etc/httpd/conf/httpd.conf is never overwritten (unless DirectAdmin is reinstalled) so any changes you make will be safe.
Source: http://directadmin.com/
How to create Custom Name Servers for your domain.
1. Ensure that your domain registrar allows you to create custom nameservers with your domain name.
2. Choose the prefix you wish to use with your domain, e.g. ns1.yourdomain.com ns2.yourdomain.com
3. Set them up using the two IP addresses that you have for DNS at the registrar domain manager. You will need to contact you provider to obtain these IP addreses.
4. Ask your data centre to enter a reverse DNS pointer for your nameservers.
5 .Now–> WHM–>>Server Setup >> Enter ns1.yourdomain.com in the Primary Nameserver field. Hit ‘Assign IP Address’, then hit ‘Add an A Entry for this nameserver’.
6. Repeat this process for Secondary.
