Solusi menggunakan 1 domain di 2 hosting dengan fungsi (e-mail dan web) yang berbeda dan provider yang berbeda

Misalkan anda memiliki 1 ( satu ) domain , kemudian memiliki 2 hosting yang berbeda provider. Nah anda misal ingin menggunakan hosting yang pertama untuk data email dan hosting yang kedua untuk data website / isi website nya. mungkin anda berfikir sulit uutuk menggunakan 1 domain untuk 2 hosting tersebut yang berbeda fungsi tiap hosting nya.

Solusi

misal :

nama domain : test.com

hosting :
1. hosting A , ip server : 111.68.112.11
2. hosting B , ip server : 75.64.116.40

Name Server (NS) provider
1. hosting A >> ns1.jojo.com & ns2.jojo.com
2. hosting B >> ns1.bubi.net & ns2.bubi.net

fungsi :

1. hosting A untuk e-mail / webmail
2. hosting B untuk data website / isi website

Setting NS ( Name Server ) domain

Untuk Name Server domain nya di arahkan ke NS hosting A yaitu ns1.jojo.com dan ns2.jojo.com

Setting A record Domain

  • login ke cpanel hosting A
  • kemudian pilih menu Advanced DNS Zone Editor
  • kemudian edit di bagian record untuk ip server nya ( masukan ip server hosting B )

test.com. 14400 IN A 111.68.112.11

jadi

test.com. 14400 IN A 75.64.116.40

kemudian buat record baru ( add new record )

Name:smtp.test.com
TTL:14400
Type: A
Address: 111.68.112.11 ( address nya = ip server hosting A)

Sekarang tinggal di Test ( untuk setting record ini di butuhkan waktu propagasi maksimal 1×24 jam )

test domain :

masuk ke cmd ( command promt pc / laptopnya) , kemudian ketikan command berikut

ping test.com

kemudian enter , jika sudah mengarah ke ip hosting B ( ip = 75.64.116.40 ) berarti sudah benar dan sudah resolve

untuk test webmail nya :

untuk akses webmail harus melalu ip server
jadi jika hosting A menggunakan cpanel , maka akses webmail nya
http:111.68.112.11//webmail

dan apabila hosting A menggunakan Spanel
maka tanyakan ke support hosting A , cara untuk akses webmail dari temporary IP

akses mail dari outlook / thunderbird / mail client yang lain

gunakan host (outgoing dan incoming) : smtp.test.com / ip server hosting A 111.68.112.11

Kesimpulan :

Jika Settingan nya sukses, maka domain sudah mengarah ke hosting B dan akses mail tetep di hosting A

semoga dapat membantu 馃檪

Cloudlinux (CageFS) make your share hosting safe

Cloudlinux (CageFS) make your share hosting safe

cloudlinux

CloudLinux was founded in 2009 to address the distinctive needs of web hosting providers. The company鈥檚 headquarters is in Princeton, New Jersey, and its development team, which is composed of employees with an appreciable proficiency in the hosting business, is based in Donetsk, Ukraine. CloudLinux is a stable privately funded company geared toward providing the ideal OS to make even the most intricate and divergent hosting needs more straightforward and less complicated.

Benefit

Cleaning up a hacked server is a nightmare. Yet, defacement and hacked accounts is something hosters battle on a daily basis. Beyond taking your support team’s time, it also tarnishes your company image and causes customers to leave in droves.The main reason hacking is so easy on shared hosting servers is because Linux was never meant to be used by a large number of not vetted users. It is too easy for a hacker to obtain an account on your server (by using a stolen credit card and signing up or by abusing some outdated script one of your customers has not updated for years). After that, a hacker has inside access to the server and can begin poking around, finding low hanging fruit and hacking your server.

CloudLinux stops that. With our CageFS and SecureLinks technologies, users are virtualized to their own file systems, preventing any individual user from seeing any other users on the server.

Beyond that we

路 Allow user access only to safe files
路 Remove user’s access to ALL SUID scripts
路 Limit customer’s access to /proc filesystem
路 Prevent symbolic links attacks
路 Customer can see only his or her own processes

All that without the need for the customer to change his or her scripts or to adjust anything at all. CageFS is completely transparent for the end user, yet impregnable to a hacker.

How To Install

To install CageFS:

$ yum install cagefs
$ /usr/sbin/cagefsctl –init

That last command will create skeleton directory that might be around 7GB in size. If you don’t have enough disk space in /usr/share, use following commands to have cagefs-skeleton being placed in a different location:

$ mkdir /home/cagefs-skeleton
$ ln -s /home/cagefs-skeleton /usr/share/cagefs-skeleton

On cPanel servers, if you will be placing skeleton into /home directory, you must configure the following option in:
cPanel WHM WHM -> Server Configuration -> Basic cPanel/WHM Setup -> Basic Config -> Additional home directories
Change the value to blank (not default “home”)
Without changing this option, cPanel will create new accounts in incorrect places.
CageFS will automatically detect and configure all necessary files for:

鈥 cPanel
鈥 Plesk
鈥 DirectAdmin
鈥 ISPmanager
鈥 Interworx
鈥 MySQL
鈥 PostgreSQL
鈥 LiteSpeed

Web interface to manage CageFS is available for cPanel, Plesk 10+, DirectAdmin, ISPmanager & Interworx. Command line tool would need to be used for other control panels.

Once you initialized the template you can start enabling users. By default CageFS is disabled for all users.

Hacked By Eriseptiawan pada Joomla

Hacked By Eriseptiawan pada Joomla

-[[--[[--[By Eri_septiawan]--]]--]]-

Mungkin anda pernah mengalami joomla anda di hack oleh orang yang tidak bertanggung jawab , salah satunya adalah Hacked By Eriseptiawan.

Solusi :

  • login ke cpanel hosting nya
  • kemudian masuk ke menu filemanager
  • kemudian setelah masuk ke root / public_html cari file index.php ( bisanya file ini yang di inject / di rubah isinya sama yang hack )
  • setelah itu open file tersebut
  • kemudian hapus semua isi coding / script nya
  • ganti dengan index.php original , atau anda bisa download dulu file joomla original nya.
  • kemudian cek juga file index.php template nya, biasanya ada di folder template , kemudian masuk ke template yang aktive sekarang
Tips to optimize your Joomla security

Tips to optimize your Joomla security

joomla

To optimize your joomla security , you can learn this solution .

Change the default database prefix (jos_)

Most SQL injections that are written to hack a Joomla! website, try to retrieve data from the jos_users table. This way, they can retrieve the username and password from the super administrator of the website. Changing the default prefix into something random, will prevent (most / all) SQL injections.

You can set the database prefix when installing your Joomla! website. If you’ve already installed Joomla! and want to change your prefix, do the following:

  • Log on to your Joomla! back-end.
  • Go to your global configuration and search for the database
  • Change your database prefix (Example: fdasqw_) and press Save.
  • Go to phpMyAdmin to access your database.
  • Go to export, leave all default values and press Start. Exporting the database can take a while.
  • When done, select all code and copy it to notepad (or any other text editor)
  • In phpMyAdmin, select all tables and delete them
  • In notepad, do a Search & replace (Ctrl + H). Set the searchterm to jos_ and change it into your new prefix (Example: fdasqw_). Press “Replace all”.
  • Select everything in your notepad file and copy it. In phpMyAdmin, go to SQL, paste the queries and press Start.

Read More »

WordPress kena hack Down By DCA

WordPress kena hack Down By DCA

Jika wordpress anda terkena hack janganlah panik , hal pertama yang anda lakukan andalah melihat cpanel anda kemudian masuk ke menu filemanager dan lihat apakah file – file wordpress nya ada yang mencurigakan.

berikut salah satu nya hack Down By DCA : penampakan nya seperti ini

IDCA Was Here

Solusinya :

  • login ke cpanel hosting nya
  • kemudian masuk ke menu filemanager
  • kemudian setelah masuk ke root / public_html cari file index.php ( bisanya file ini yang di inject / di rubah isinya sama yang hack )
  • setelah itu open file tersebut
  • kemudian hapus semua isi coding / script nya
  • ganti dengan index.php original biasanya script nya sbb :

<?php
/**
* Front to the WordPress application. This file doesn’t do anything, but loads
* wp-blog-header.php which does and tells WordPress to load the theme.
*
* @package WordPress
*/

/**
* Tells WordPress to load the WordPress theme and output it.
*
* @var bool
*/
define(‘WP_USE_THEMES’, true);

/** Loads the WordPress Environment and Template */
require(‘./wp-blog-header.php’);
?>

  • kemudian save , lalu coba di refresh web browsernya

semoga dapat membantu 馃檪