Instalasi CentOS

Bagi teman-teman yang senang ngutak-ngatik server, atau yang senang dengan OS yg berbasiskan linux. Saya punya pengalaman tersendiri dalam menyiapkan sebuah server, dalam waktu yang tidak sampai satu rokok jie sam su habis, server ini sudah kelar digunakan. Tentu saja supaya server ini berguna hingga bisa mengudara, anda harus punya jaringan internet sekaligus dengan IP Public (Static) yang disediakan oleh ISP anda. Paling tidak anda harus sudah menyediakan dua IP address. IP local dan IP Public. IP local untuk memudahkan anda masuk melalui jaringan local dan lebih cepat, hampir tanpa kendala. Sedang kalau menggunakan IP Public pun sebetulnya juga tidak masalah. Kelebihannya, kalau dengan IP Public anda bisa mengaksess server anda dari manasaja dan di manasaja anda berada. Kekurangannya, IP Public itu bukan milik kita murni. Jadi jika pada kondisi tertentu (katakanlah diblokir oleh ISP anda karena satu dan lain hal), maka anda tidak bisa masuk lagi melalui IP ini. Kita mulai saja: Pertama, anda harus menyediakan software CentOS Server ini dengan cara download. TIdak terlalu besar sih ukurannya, sekitar 600 Mb, tepatnya 580Mb. Yah« 1 CD saja: Anda bisa memilih cara download dan jenis filenya; ada dua: 1. Jika anda menggunakan OS windows anda bisa langsung download ke alamat ini : http://vault.centos.org/4.4/isos/i386/CentOS-4.4.ServerCD-i386.iso 2. Jika sudah selesai downloadnya, anda tinggal memburning pake nero atau ashampo atau software burning lainnya kesukaan anda. Sediakan satu blank cd untuk diburning di media ini. 3. Jika sudah selesai, maka anda telah memiliki satu master cd CentOS Server versi 4. Kedua, sediakan satu mesin computer yang akan dijadikan server oleh anda. Semakin besar spesifikasinya semakin baik. Kalaupun pakai Pentium III pun sebetulnya sudah bisa dengan kapasitas Hardisk 30 G dan RAM minimal 512 kb atau 1024 kb. Ini adalah ukuran minimalis untuk server web yang tidak terlalu besar muatannya. Tapi jika anda mempunyai spesifikasi server yang handal (seperti XEON dari HP mutakhir, misalnya) itu sangat dianjurkan.

anda harus pilih ini jika anda hendak menggunakan MYSQL sebagai basis data di server anda. Misalkan 192. Tinggal ok dan next. LAN Card OnBoard. MYSQL Server. Kemudian anda restart computer anda. partisi di linux dengan di windows sangat berbeda.156. dengan nama : eth1 IP:222. ( Ini disarankan bagi yang servernya cukup handal dan belum . Berarti anda cukup menyediakan satu LAN Card saja. Sebab dengan sendirinya linux akan secara otomatis mengatur partisinya dengan baik. Ada dua pilihan untk memulai menginstall ini: Pertama berbasiskan GUI.156.134. sebaiknya jangan menggunakan Firewall bawaan dari CentOS.168. Atau pilih juga POSTGRESQL jika anda termasuk pecinta POSTGRE.7. Ketika ada option untuk costumasi server. Terkecuali ketika ada option tentang firewall. Anda tinggal perhatikan secara seksama. Pertama masukkan CD CentOS Server anda ke Driver. Gambarnya sbb: 1. LAN Card External. Firewall bisa kita sediakan sendiri setelah installasi selesai. Ketika tampilan pertama muncul.134. jika anda hendak mengembangkan server anda untuk mail server juga. dengan nama : eth0 IP: 192. Pada saat option muncul sebelum installasi. Jika tidak.170. Dari model kedua ini anda hampir sepenuhnya menggunakan text. Dan biarkan linux untuk auto configurasi. Kita asusmsikan masingmasin LAN Card ini. Jadi PostgreSql tidak saya checklist. antara yg berbasis text dengan GUI). tapi masih juga dibantu dengan grafis-grafis ringan untuk interaksi dengan anda. Jangan lupa untuk mencheklist. Saya sarankan. akan dibuat artikel tersendiri. Kalau saya masih setia pada MySQL. Kedua berbasiskan text. harus dipilih sebab didalamnya terdapat httpd dari apache yang akan menggerakkan server anda untuk bisa menampilkan halaman web. tinggal klik saja.170 Kita mulai install.> Anda pun bisa menchecklist Mail Server. Karena didalamnya disiapkan software Bind (named) untuk manajemen domain. Web Server. Lebh baik Firewall jangan diaktifkan. Untuk menyaipkan manajemen domain. Ada beberapa hal prinsip yang harus anda perhatikan: Ketika option untuk mengatur partisi. jika anda akan membuat server dns sekalian pada server ini. anda tinggal pilih remove all partition.50. artinya anda menginstall dengan full tampilan yang familiar.Jangan lupa untuk menyiapkan dua LAN Card. Dan akan kita bahas pada artikel sendiri.50. dengan nama: eth0 untuk IP local. untuk install pertama. Perlu diketahui. untuk sementara klik pakai spasi di checklist DISABLE-nya ( option ini hampir sama. Kalau CPU anda menyediakan LAN onboard. antara lain: DNS server. pilih ini. Anda tidak perlu pusing-pusing mikirkan ini.168.7 2. Sedangkan LAN Card lainnya kita namakan: eth1 misalkan 222. Maka tidak perlu dichecklist.

101. Ketika masuk pada opsi manajemen IP.134.20. Defaultya localhost.google.155 Perhatikan baik-baik. jika tidak ada aral melintang... Improving the speed of hostname lookups 2. Jangan dichecklist DHCP-nya. Secondary Server yang diberikan oleh ISP anda. Anda tinggal minum kopi sambil mengisap ji sam su ( bagi yg suka rokok) menunggu sampai selesai install.2. GO! Install.localdomain anda bisa mengganti dengan sidukun. Pada tahap ini.240 atau disesuaikan dengan netmask dari ISP anda.domain.255.200 Primary Server : 202. Hal ini akan bisa dilakukan ketika server telah selesai diinstall.com to IP addresses 100.13. berarti anda sukses installasi server anda. 1.240 atau disesuaikan dengan netmask dari ISP anda.168. By far the most popular DNS Server software out there is a package called bind. Berikutnya.. untuk Card yang inisialnya eth0 anda isi dengan no IP 192.7 netmask 255.250.! Jika masih penasaran. Demikian juga eth1 dengan no IP 222. Managing your own intranet hostnames & IP addresses in a central location .170 netmask 255. Linux akan dengan pintarnya mengolah file-filenya di server anda.. Sebagaimana yg kita tentukan sebelumnya. Setup a DNS Server on CentOS 5 This is a pretty geeky thing to do but running your own DNS Server on your intranet does make some sense from a performance and conveience perspective.50. Background The sole purpose of a DNS Server is to provide a look-up service for mapping hostnames e. www. anda bisa kontak saya unt sharing.134. dengan menggunakan perintah YUM INSTALL. Anda tidak perlu khawatir urusan dengan software yang tidak terinstall. Kemudian isi nama server anda dengan nama favorit anda sendiri. akan ada artikel tersendiri.156. Atau langsung saja pada langkah instalasi.ada mesin server lain untuk dijadikan mail server). Primary Server.2.g. apa-apa yang perlu untuk di server anda nanti.255.5 Secondary Server : 202. Horeeee. jangan lupa untuk mengisi Gateway. There are essentially 2 reasons to running your own DNS Server.255.245.255.0. Masukkan no Gateway. Untuk bab membuat mail server.com atau apa saja kesukaan anda. Misalnya: Gateway: 222.

and manage these in one stop rather than having to manage them throughout your intranet. 1 yum install bind bind-utils bind -libs Generating a rndc key NOTE: All the config files we¶re going to work on are located in /var/named/chroot Next you¶ll need to create/modify a rndc. In essence by having one machine provide all hostname look-ups in your intranet. mail. etc.conf . # End of rndc.0. The file should be rndc.key file. secret "nHFS3WOpdap75IvsYSXVNYWusnAQPT6z5XC8V5YPWXnZ8RN8tdfSFuClZ8nNouWyGhvHB8mE TJgwsrvhiYhIhA==" .conf key "rndckey" { algorithm hmac -md5. default-port 953. Additionally once a name is looked up your DNS Server will cache the results for a set period of time so that subsequent queries can come out of your DNS Server¶s cache and not have to go and do the look-up on your ISPs DNS Server. This file contains a key which is required in order to manage the bind service once it¶s up and running.key. options { default-key "rndckey" . default-server 127. 1 2 3 4 5 6 7 8 9 1 0 1 1 1 2 # Start of rndc. In so doing this it¶s much easier to connect to systems using names rather than IP addresses.The first reason is what is commonly called a Caching Name Server. It just makes more sense to me. Plus it¶s fun to name all the systems! Taking this a step further you can create generic hostnames such as imap.1. you¶re cutting down on every machine in your intranet having to independently look-up names. ntp. Since you control the DNS Server you can create your own local domain (called zones in bind lingo) and name all the systems within your intranet. With this key you can theoretically manage bind either on the host where it¶s running or you can manage it on any system that is allowed to do so and knows this key! 1 # command to generate a new 512 byte key 2 rndc-confgen -b 512 This command will return the following output which you¶ll want to either redirect to a file or copy and paste into a file.conf and/or rndc. The second reason is actually the cooler one. /var/named/chroot/etc/rndc. Getting started First things first.conf but I like to use this name instead.0. }. pop. }. install the necessary bind software. smtp.

1 uses an unprivileged * port by default.0.1 port 953 allow { 127.conf file Now let¶s flesh out that named. forwarders { # the following IP addresses are my ISPs DNS Servers. 24. but BIND 8. }.conf. adjusting the allow list as needed: key "rndckey" { algorithm hmac -md5.1. }. # controls { inet 127. forward only.92.0.92. /* * If there is a firewall between you and nameservers you want * to talk to.168.41.conf.0. This goes into the file /var/named/chroot/etc/named.0.1. }.pid" . */ .conf file a little bit more. Make sure to remove the comments at the beginning of each line to turn them on. 127. These will be used for looking up # hostnames that I don't locally manage. dump-file "named_dump. }.The rndc-confgen command also returns some additional output below. logging { category default { default_syslog. the REST OF THE INTERNET! # my ISPs DNS Server #1 24. }.0. i . } keys { "rndckey".0. }.0 /24.1. secret "nHFS3WOpdap75IvsYSXVNYWusnAQPT6z5XC8V5YPWXnZ8RN8tdfSFuClZ8nNouWyGhvHB8mE TJgwsrvhiYhIhA==" . you might need to uncomment the query -source * directive below. }.e. options { pid-file "/var/run/named/named. controls { inet 127.1 port 953 allow { lan. }.conf named.0. category lame -servers { null.40. }. Previous versions of BIND always asked * questions using port 53. # End of named.db" .226. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 acl lan { 192.0. # my ISPs DNS Server #2 }. 1 2 3 4 5 6 7 8 9 1 0 1 1 # Use with the following in named. directory "/var/named" .226. } keys { "rndckey" .

allow-query { lan.net´ includes all the hostnames and the IP addresses they point to. zone "1. Here is a quick rundown of what¶s going on here. allow-recursion { lan.arpa´.in-addr. Bulding zone files The first zone: ³bubba.bubba. allow-transfer { lan. file "data/db.168.arpa´ and ³1.net" { type master.in -addr.168. .101 The fourth zone: ³.168. file "data/db.1.net´ looks like. So these would be my systems: y y y scully.0/24 and 127.net mulder.168. }.0/24 means IP addresses in the range 192. ³0. These are when you look up a IP address and want to know what name(s) are associated with it.127. ³1. }." { type hint.168. Here is what the zone ³bubba. }.192.255.net´. }.arpa´ are special zones that provide ³reverse´ name look-ups.0.1. For example: y y 192.1.1" .127.0.in-addr. }.0. }. zone "0.168. }. The acl lan creates an access control list that includes 192.168.168.100 192.192.192.0" .in-addr.36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 query-source address * port 53. and ³.hints" .1.in -addr. and the results cached here for subsequent quereies.192.168. These hostname and IP address look-ups will be forwarded to my ISPs DNS Server.0. for any hostnames and IP addresses that fall outside of the first 3 zones.in-addr. 192.168.net The second and third zones: ³0. The zones.0. zone "bubba.1 ± 192.0. file "data/db. }.´ are all essentially files containing either hostname IP address mappings or IP address hostname mappings that this bind server will be responsible for.net doggett.1 so that only hosts within these IP address ranges can remotely manage and use this bind instance.127.arpa" { type master.1.bubba.´ is a special zone that makes this bind server act as a caching name server.arpa´.1.127. ³bubba.arpa" { type master. file "root.bubba. zone ".bubba.net" .

IN HINFO "Celeron 450" "Windows 2000 " scully.bubba. . ( 2000072802 . Here is what the zone ³db.net.168.101 .bubba. IN MX 10 mail. . .1 .net.net. IN A 192. @ IN MX 20 mail. serial 28800 ..net.net.net.bubba. hostmaster.net.bubba. expire 86400 . Provide familiar names to services but .2GHz" "LINUX" mulder.net.bubba.net. ... Each hostname gets 4 lines. .. These setup a TTL or Time To Live which means how long any of this data should be cache. ----------------------------------------------------------bubba. IN MX 10 mail. default_ttl ) @ IN NS ns. acutally all are coming from XXXXX . I only have one mail exchange so I just list it twice.168.. IN A 192.bubba. . ------------------------mulder.168. IN HINFO "AMD Athlon(tm) Dual Core Processor 4850e 2.168. IN A 192. hostmaster.bubba. Line 14 denotes which machine is the SOA.1.192. @ IN SOA ns. Mandatory minimum for a working domain .net. Subnet 192. The ³IN HINFO³ which is just a description of the host itself.bubba.bubba.bubba.bubba. retry 3600000 .net.1 looks like. scully. These need to be bound to the address directly.net. Lines 15 & 16 state which machine is the mail exchange for this domain. mulder.1 mulder. no CNAME 's.net. .bubba.net is the master of this domain is what it¶s saying 8-).bubba.net.bubba.1 machines .net. IN A 192.1. refresh 7200 .net. hostmaster..net..bubba. Start of Authority. The first 16 lines are pretty standard..1. The most important section in this file starts with the declaration of hostnames. IN TXT "" scully.bubba.1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 $TTL 604800 . Zone file for bubba. @ IN MX 10 mail.168. And finally the ³IN TXT³ line which I¶m not going to get into today but it is important later on when you¶re setting up you mail server.net. IN A 192.bubba. The ³IN MX´ states who the mail exchange is for this host. .168.1.1. 1 2 $TTL 604800 @ IN SOA ns.net.bubba. ( .101 ns.bubba.168. IN TXT "" . ns. A ³IN A´ line which tells you the IP address for this hostname.bubba.net .net.2 scully.

net . ->>HEADER<<.bubba. ns .NET.net. .net. J. The first 9 lines are essentially stating how long any Caching DNS Name Server should cache this data before getting a fresh copy. 101 102 103 .´ uses a file called root. default -ttl ) IN NS ns.ROOT -SERVERS.net. . ANSWER: 13.NET.ROOT -SERVERS.NET. ..net.NET. ( @ . ANSWER SECTION: .. flags: qr aa rd.ROOT -SERVERS. default_ttl ) NS ns.4 -P1 <<>> @e. AUTHORITY: 0. Here is what my zone file looks like: 1 2 3 4 5 6 7 8 9 10 11 $TTL 604800 @ IN SOA ns.bubba.ROOT -SERVERS..net. retry 604800 . L. .127. <<>> DiG 9.net. The SOA ns. QUESTION SECTION: .root-servers. status: NOERROR.net. F.NET.bubba. . serial 28800 .NET.. .NET.ROOT -SERVERS.0.. retry 604800 . The hostmaster. . 1 IN IN localhost. 2000072801 .ROOT -SERVERS. serial 28800 . IN IN IN PTR mulder.ROOT -SERVERS..NET. . expire 86400 . C.. G.hints..bubba.bubba. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 . B. PTR hostmaster.ROOT -SERVERS.bubba.3.net is actually an email address that is responsible for this domain. QUERY: 1. hostmaster@bubba.bubba.net.. (1 server found ) . 518400 518400 518400 518400 518400 518400 518400 518400 518400 IN IN IN IN IN IN IN IN IN IN NS NS NS NS NS NS NS NS NS NS D. I. global options: printcmd .net is saying which machine is the authority for this domain. expire 86400 .bubba. PTR scully. The zone ³. . M. Got answer: .bubba.net. PTR doggett. ADDITIONAL: 14 .bubba. 2000031801 .3 4 5 6 7 8 9 10 11 12 13 14 15 @ . . .opcode: QUERY.ROOT -SERVERS.NET. refresh 7200 .. Here is an example of what this file looks like. Finally the zone ³db..0 which really serves no purpose other than as a backup in case a host didn¶t configure itself correctly with the loopback address. id: 21247 . refresh 7200 .

10 #53(192..ROOT-SERVERS.230.201 192.NET.33.6 3.ROOT-SERVERS. B. .NET.36. H.NET.203. dig.4 2001:503:ba3e::2:30 192.90 192.203. -SERVERS..NET.NET.17 192. . .. The /etc/resolv.NET. F.. E.. -SERVERS. A.5. .ROOT-SERVERS..112.. .ROOT-SERVERS.58. or nslookup.0.ROOT -SERVERS. I. You can accomplish this by changing 2 files.ROOT-SERVERS.21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 ..228.128..ROOT-SERVERS.ROOT-SERVERS. files dns Taking it out for a test drive You can see if it¶s working by poking the name server using host. J.10) WHEN: Fri Feb 20 03:49:01 2009 MSG SIZE rcvd: 500 Starting bind up Once you have all this in place you can start up bind with this command.203. D.NET.NET.NET.30 2001:503 :c27::2:30 Query time: 109 msec SERVER: 192.5.1.230.10 192. hosts: . .ROOT-SERVERS. /etc/resolv. C.NET.36. .148. 1 /etc/init.ROOT A. 198. ..4 128.8.ROOT-SERVERS. J.53 2001:500:1::803f:235 192.101 The /etc/nsswitch.79.NET.4. Here are a couple of example quereies.12 128.241 2001:500:2f::f 192.NET. .conf.NET.ROOT E.ROOT-SERVERS. 518400 IN 518400 IN 518400 IN 518400 IN 3600000 3600000 3600000 3600000 3600000 3600000 3600000 3600000 3600000 3600000 3600000 3600000 3600000 3600000 IN IN IN IN IN IN IN IN IN IN IN IN IN IN NS NS NS NS A AAAA A A A A A AAAA A A AAAA A A AAAA K. G.net nameserver 192.NET.conf should look like this: 1 2 search bubba.ROOT-SERVERS.10.NET.ROOT-SERVERS.d/named start Configuring a host to use your DNS server One final step is to configure your host to use your newly setup DNS Server as it¶s name server.ROOT-SERVERS. ADDITIONAL SECTION: A.. -SERVERS. .41..230.ROOT H..conf should have an entry like this in it: 1 2 3 4 5 . .NET. H.NET.NET.conf and /etc/nsswitch.ROOT-SERVERS.168.2. F.

1.bubba.. 604800 604800 IN IN IN A A NS 192. ANSWER SECTION: ns.bubba.net. .168.1.168. ANSWER: 1. global options: printcmd .1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 # host example % host -l bubba.101 #53(192.. . status: NOERROR..ns.168.1. <<>> DiG 9. QUERY: 1.net bubba.1.conf remove this line UserDir disable and uncomment this line UserDir public_html (or can just change the first line) Then restart the server /usr/sbin/apachectl restart . ..1.101 ns.bubba.opcode: QUERY...168. .3.. id: 54856 ..168.1 .101 Enable user directory (public_html) edit /etc/httpd/conf/httpd. ADDITIONAL: 0 . # dig example % dig ns.1. Got answer: . .net.net ...1.101) WHEN: Sat Feb 28 20:54:46 2009 MSG SIZE rcvd: 60 # nslookup example % nslookup ns.bubba. .bubba. .168.net.net.168.net.net .bubba. Query time: 1 msec SERVER: 192... bubba..101 #53 Name: ns. AUTHORITY SECTION: bubba.net Server: 192.. QUESTION SECTION: .net name server ns.bubba.bubba.. AUTHORITY: 1. flags: qr aa rd ra.net has address 192.4 -P1 <<>> ns.101 Address: 192. ->>HEADER<<.net Address: 192.

com dan domaindua.0. 4. contoh kita punya dua domain yaitu domainsatu. wget -N http:/ /layer1.1 kemudian kita ingin semua domain tadi mempunyai website yg berbeda-beda.If SELinux is enabled (I did). 1.cpanel. 3. /usr/local/cpanel/cpkeyclt ² Activates your license after installation.ent. sh latest ² Opens and runs the installation files. you must also need to run these /usr/sbin/setsebool -P httpd_enable_homedirs true chcon -R -t httpd_sys_content_t /home/user-abc/public_html (do not forget to change the path on the second line) Cara Install CPanel di CentOS Submitted by admin on Mon. 2.200. cd /home ² Opens the directory /home . Maka otomatis CPanel akan terinstall di CentOS! Konfigurasi Virtual Host di CentOS Apa itu Virtual Host? Virtual host berguna untuk pengaturan website atau URL dalam satu mesin atau satu IP.com tetapi kita hanya punya satu mesin dengan IP 192.ent.0.centos4 . Dengan konfigurasi pada virtual host kita dapat menyelesaikan masalah ini. check package apache [root@rhesanu ~]# rpm -qa http* httpd-2.52-41.centos4 httpd-suexec-2. Caranya sbb: 1. 04/26/2010 .200.01:12 y y Tips & Tricks cpanel Cara install CPanel di CentOS sangat mudah.net/latest ² Fetches the latest installation file from the cPanel servers. karena CentOS adalah salah satu OS yang direkomendasikan oleh CPanel.52-41.

Untuk melihat hasilnya kita dapat menambahkan file php pada domainsatu dan domaindua [root@localhost ~]# nano /var/www/html/domainsatu.1:80> ServerAdmin webmaster@domaindua.com´.com-error_log CustomLog /var/log/httpd/domaindua.conf edit baris ini NameVirtualHost 192.com/public_html/ [root@localhost html]# mkdir -p /var/www/html/domaindua.0.com DocumentRoot /var/www/html/domainsatu.52-41.0. Buat direktori untuk pengaturan domain [root@localhost html]# mkdir -p /var/www/html/domainsatu.200.com-error_log CustomLog /var/log/httpd/domainsatu.com/public_html/ pastikan direktori tersebut berada di document root.com ErrorLog /var/log/httpd/domaindua.com/public_html/index.200. Edit file /etc/httpd/conf/httpd.com/public_html/index.com-access_log common </VirtualHost> <VirtualHost 192.52-41.php <?php echo ³this is domaindua.1:80 kemudian tambahkan baris ini <VirtualHost 192.com ErrorLog /var/log/httpd/domainsatu. 3.ent.php <?php echo ³this is domainsatu.com´.1:80> ServerAdmin webmaster@domainsatu.com DocumentRoot /var/www/html/domaindua. Kemudian restart apache [root@localhost ~]# service httpd restart . ?> 5.200.conf [root@localhost html]# /etc/httpd/conf/httpd.200.httpd-manual-2. ?> [root@localhost ~]# nano /var/www/html/domaindua.centos4 httpd-devel-2.ent.com/public_html ServerName domaindua.centos4 2.com-access_log common </VirtualHost> 4.com/public_html ServerName domainsatu.200.200.

com berisi domainsatu. lihat gambar dibawah ini: . seperti gambar di bawah ini tetapi pada saat kita menambahkan url dengan www.com dan www.Stopping httpd: Starting httpd: [ OK ] [ OK ] setelah itu coba browsing domainsatu.domaindua.domaindua.com ada masalah.com dan domaindua.domainsatu.com.com. www.

untuk masalah diatas tambahkan server alias pada file /etc/httpd/conf/httpd.conf tambahkan baris di bawah ini ServerAlias www.domaindua.com kenapa berisi isi dari domainsatu.com??? 6.Perhatikan pada alamat url dan isi url ada kesalahan pada www.com pada domain ini benar tetapi perhatikan pada www.domaindua.com berisi this is domainsatu. [root@localhost ~]# /etc/httpd/conf/httpd.com lihat gambar dibawah ini: setelah itu lihat hasilnya: .domain satu.conf.

You can do that by running the below command. the first step is to make sure you are logged into your shell. next we will want to move. etc as the cPanel installer will take care of it all for us. I am going to assuming you know the basics of a shell (aka using SSH as some would say. how to i stall cPanel/ HM on Cent I will be using Cent 5. the next command will be to make the µcpinstall¶ folder in your /home directory. the screen should look something similar to below. this will be the same for RedHat and for 32-bit also. if your running Windows I recommend PuTTy). # mkdir /home/cpinstall This will make the necessary folder on the file system for us to start with. you can do that by running the code below.5 64-bit as my base OS. Ok.How to i tall cPanel/ HM on CentOS Hell l e will be st ti wit t e basi s. First we need to start with a fresh install of CentOS. you don¶t need to install anything li e Apache. or as some will know it as µcd¶ into that folder. # cd /home/cpinstall . MySQL. Once we are both there. When reading this tutorial.

Depending on how fast the system is. This file is always updated. Usually for me. we will need to download the appropriate file to start the cPanel install.Now that we are there. I can say it takes about 2 hours. we can start the install process. this can take anywhere from 30 minutes to 4 hours. # sh latest After running that code. and how fast your network connection is.net/latest If everything goes well with that. so by running the below command you¶ll always get the newest version of cPanel installed on your server/ PS. You can in voke the installer by running the command below. Now that we are upto this point. you should see a cPanel logo come on the screen and the install will start. # wget http://layer1. your shell window will look something like this.cpanel. Once the . There will be no need for any user intervention unless there is a problem.

screen looks like below you are safe to walk away. Once the install is complete your SSH screen will look something like this: .

you¶ll get a screen like this: Your default login username is µroot¶. it was telling me I need to restart my server. Once this is done. Once restarted. and your password is your root password .In my case. you can access the WHM by going to http://IPHERE:2086.