netstat -tan | grep ‘:80 ‘ | awk ‘{print $6}’ | sort | uniq -c

netstat -anp |grep ‘tcp\|udp’ | awk ‘{print $5}’ | cut -d: -f1 | sort | uniq -c | sort -n

1. Regiser your domain
Register the domain name you would like to use, you can register a domain here if you need one.This domain will be used as your nameservers – eg ns1.yourdomain.com and ns2.yourdomain.com

2. Additional IPs
Have 2 available IP addresses for your server that aren’t in use.You will need to contact you provider to obtain these IP addreses.

3. Registering the Nameservers
Now login to your domain management page for the domain you registered and  register ns1.newdomain.com and ns2.newdomain.com as nameservers (registries normally have a special facility for doing that). The registry may also have a facility to propogate these nameservers around the foreign registries – if so, you should use this facility.

These registrations may take a few days to propagate (often as many as 3 days).

4. Reverse DNS
You may also need to get your data centre to enter a reverse DNS pointer for your nameservers. You’ll need to let them know each nameserver and its IP address. Sometimes you can suffer non-delivery of mail if you don’t so this. Reverse DNS pointers can take a while to propagate.
Setup a reverse on the IP address for your domain

5. Broken NDC/BIND
My version of WHM/CPanel came with a broken NDC. To fix this:

SSH into your box as root.

(a) Type: cd /scripts
(b) Type: ./updatenow
(c) Type: ./fixndc

Go back into WHM, go to the Restart Services section in the left menu and click DNS/Nameserver (BIND).

You will need to do this if you start getting ‘ndc’ errors when you are doing anything DNS related in WHM.

6. Setup Nameservers In WHM
Go into WHM (Web Host Manager) and select Edit Setup from the Server Setup menu on the left. Enter ns1.newdomain.com in the Primary Nameserver field. Hit ‘Assign IP Address’, then hit ‘Add an A Entry for this nameserver’.
Repeat this process for the Secondary Nameserver field.

7. Tidy Up Junk Nameservers
Go into WHM (Web Host Manager) and select Manage Nameserver IPs from the Server Setup menu on the left. Remove any nameservers you don’t recognise. This is just a tidy up exercise in case anyone’s set anything up on the box before you.

8. Initial Nameserver Setup
Go into WHM (Web Host Manager) and select Initial NameServer Setup from the Server Setup menu on the left. Run this.

9. Restart BIND
Restart BIND (step 7 restarts BIND, but we’ve known it to need a proper stop and start for it to work) from SSH with:

service named stop
service named start

10. Manual Checks
I don’t know what it is about this process, but it doesn’t always work, so there are some things you can check manually via SSH.

/etc/wwwacct.conf
Check that the nameservers are correctly specified on NS, NS2 etc.
EG: scroll to the name servers section…..
NS ns1.yournameserver.com
NS2 ns2.yournameserver.com

/etc/resolv.conf
Check that there are nameserver entries for each IP. There may also be one for 127.0.0.1 – this is okay. I’m led to believe (by the ‘man’ entry for resolv.conf) that this isn’t a particularly important file, but I changed mine to read:

domain mybox.com
search mybox.com
nameserver 127.0.0.1
nameserver 111.111.111.111
nameserver 222.222.222.222

Where ‘mybox.com’ is the main domain of my server, and ‘111.111.111.111′ and ‘222.222.222.222′ are the IP addresses of my primary and secondary nameservers.

resolv.conf is used to lookup names that are not in FQDN format.

/etc/nameserverips
Check that there are entries for each IP acting as a nameserver.
EG:
IPHERE=ns1.yournameserver.com
IPHERE=ns2.yournameserver.com

Source: webhosttgear.com

1) Go to http://www.dnsreport.com/tools/dnsreport.ch?domain=mydomain.com
2) Check for BIG RED “FAIL” (7th box, going down from up) saying “Open DNS servers”.

If you see the message, you can correct it the following way:

1) login to your server as root
2) nano -w /etc/named.conf (if you are running Bind)
3) Look for // query-source address * port 53; and right below write the following line:

recursion no;

4) Save and exit, restart Bind by typing service named restart
5) Check DNSReport.com to make sure it went right. You should not see the error message anymore.

If you run something else than Bind then please check http://www.dnsreport.com/info/opendns.htm for instructions.

Source: eth0.us

open you named.conf and add before options { the follow lines:

acl “trusted” {
xxx.xxx.xxx.xxx;
yyy.yyy.yyy.yyy;
};

where xxx.xxx.xxx.xxx is your ip address same for yyy.yyy.yyy.yyy.
for cpanel users, you can find yours ips in the follow file: /etc/nameserverips

after that, inside the options add after the line “// query-source address * port 53;” the follow:
allow-recursion { trusted; };
allow-notify { trusted; };
allow-transfer { trusted; };

also uncomment the line “// query-source address * port 53;” “to query-source address * port 53;” with out the ” (double-quotes).

restart your service.

Verify again your status with DNSreport.

Observation: you can also set up a version line it should be like:
version “Oh come on why do you want to know witch version my DNS server is ?”;

this line can be add iside your named.conf right after the line query-source address * port 53; or inside options.

Source: eth0.us

This guide is designed to help do the initial setup on a MySQL cluster in which multiple MySQL servers all serve the same content through the use of the replication function. We have successfully deployed this solution for multiple clients and it is a very good option for those needing a more powerful mysql solution. Carlos (theuruguayan) actually created this document so please direct any questions to carlos@totalserversolutions.com .

Be sure your mysql servers are running the same version before starting this guide, yes, is possible to have a few combinations of master-slave versions, for more information about this you can check:

http://dev.mysql.com/doc/refman/4.1/en/replication-compatibility.html

1 – Write down which is the setup you are going to do, which server is master and which server/s will be slave.

2 – Select your username/password for replications accounts. You can have one per server if you want, or one for all the mysql network.

3 – mysql> GRANT REPLICATION SLAVE ON *.*

TO ‘USERNAME’@'IPFROMTHESLAVE’ IDENTIFIED BY ‘PASSWORD’;

Username: mysql username
IPfromtheslave: ip from the mysql server that will be the one replicating the master db.
PASSWORD: the password for the replicator account.

Just a few side notes.

a) None of the passwords need to be root passwords.
b) Is not recomend to use only 1 user for replication in all the network.

4) In the master server you need to Flush all the tables, this will prevent clients from writing the db so it will keep without change while we copy over.

mysql> FLUSH TABLES WITH READ LOCK;

5) Make sure that the [mysqld] section of the my.cnf file on the master host includes a log-bin option. The section should also have a server-id=master_id option, where master_id must be a positive integer value from 1 to 232 – 1. For example:

[mysqld]

log-bin=mysql-bin

server-id=1

6) Login using another ssh client to the master server and lets create a snapshot.

mkdir /home/slave_db
rsync -vrplogDtH /var/lib/mysql /home/slave_db

You may not want to replicate the mysql  database if the slave server has a different set of user accounts from those that exist on the master. In this case, you should exclude it from the archive. When the rsync is finish, just login inside mysql and type:

SHOW MASTER STATUS;

Save this info in a txt file inside the slave_db folder that we will use them laster.  After you finish doing this, you can reenable the activity on the master: UNLOCK TABLES;

7)  Stop the server that is to be used as a slave server and add the following to its my.cnf file:

[mysqld]

server-id=slave_id

The slave_id value, like the master_id value, must be a positive integer value from 1 to 232 – 1. In addition, it is very important that the ID of the slave be different from the ID of the master. For example:

[mysqld]

server-id=2

Remember that server-id must be unique in all the mysql network.

Copy the files over from the slave_db folder to the remote location. You can do this doing the following command:

rsync -e ssh -avz /home/slave_db/ root@REMOTESERVER:/var/lib/mysql

Check that all the permitions and correctly in the /var/lib/mysql folder.Remember files must be own by mysql:mysql

9) Start Mysql and enter to it, write the following changing the values that are needed:

mysql> CHANGE MASTER TO

->     MASTER_HOST=’master_host_name’,

->     MASTER_USER=’replication_user_name’,

->     MASTER_PASSWORD=’replication_password’,

->     MASTER_LOG_FILE=’recorded_log_file_name’,

->     MASTER_LOG_POS=recorded_log_position;

10) type: START SLAVE;

To reset the MySQL password via WHM, simply log into WHM and select either:

1) “MySQL Root Password” (and change it) or
2) “Change a User or Database Password” (to change a specific password)

There is no reset option in cPanel for mysql database passwords. But you can overwrite existing password (as if  a reset)

To update the binary cPanel uses, create a new profile in EasyApache wherein you enable SOAP support for PHP. Save the profile and don’t build. Then copy your new profile like this (using example.yaml as the profile file name):

# mv /var/cpanel/easy/apache/profile/makecpphp.profile.yaml /var/cpanel/easy/apache/profile/makecpphp.profile.yaml.backup
# cp /var/cpanel/easy/apache/profile/custom/example.yaml /var/cpanel/easy/apache/profile/makecpphp.profile.yaml
# /scripts/makecpphp

The /scripts/makecpphp command builds a new PHP binary for cPanel to use.

Try changing the setting of log rotation here

edit /etc/logrotate.conf

and change “weekly” to “daily”