Monday, 27 February 2012

How to install/compile Apache with PHP via source installation


How to install/compile Apache with PHP via source installation?

If you like to install PHP with Apache via source installation, kindly follow the steps below.

This PHP installation is compiles with major modules like GD, MCrypt, xml,etc

1.wget http://bg.php.net/distributions/php-5.3.1.tar.bz2
2.cd php-5.3.1.tar.bz2
3.bunzip2  php-5.3.1.tar.bz2
4.tar -xvf php-5.3.1.tar
or simply do tar jxf php-5.3.1.tar.bz2
5.cd php-5.3.1
6. ./configure --with-apxs2=/usr/local/apache2/bin/apxs --with-mysql    --prefix=/usr/local/apache2/php
{This is to compile Apache with PHP alone}

./configure --with-apxs2=/usr/local/apache2/bin/apxs --prefix=/usr/local/apache2/php --with-gd[=DIR] --with-freetype-dir[=DIR]
--enable-zip
--with-xsl[=DIR]
--enable-ftp
--enable-mbstring
--with-mcrypt[=DIR]


(To know more ./configure --help)



7.make (if u do it again install do a "make clean")
8.make test
9.make install
10.If file /usr/local/apache/modules/libphp5.so does not exist or is an older version, type this (change this to libphp4.so for PHP 4):

    cp -p .libs/libphp5.so /usr/local/apache/modules

11.In httpd.conf
# Use for PHP 5.x:
#Add at the end of the file
#LoadModule php5_module        modules/libphp5.so
AddHandler php5-script php 
AddType application/x-httpd-php-source phps


# Add index.php to your DirectoryIndex line:
DirectoryIndex index.html index.php

AddType text/html       php

12.cd /usr/local/apache2/htdocs
13.vim index.php
--------------------
<?php phpinfo(); ?>
--------------------
14./usr/local/apache2/bin/apachectl restart
15.lynx www.hemanth.com
16.You should see the phpinfo page

Saturday, 25 February 2012

Installing Domainkeys, DKIM in postfix

How to install dkim and domainkeys in postfix?

DomainKeys works by signing outbound e-mail messages with a cryptographic signature which can be verified by the recipient to determine if the messages originates from an authorized system.

DKIM–DomainKeys Identified Mail. DKIM is an extension of DomainKeys. It allows a recipient to verify that a message really does come from the sending domain. Senders publish a public key for their domain and then cryptographically sign their outgoing email, using the corresponding private key. Recipients can then verify the signature, typically as part of the spam filtering process.

Prerequisites:

We can use dkim proxy to configure domainkeys and dkim in the server. DKIMproxy is written in Perl. It requires additional modules Crypt::OpenSSL::RSA, Net::DNS etc., We can use the "cpan" to install these perl modules.

---------------
cpan Crypt::OpenSSL::RSA
cpan Digest::SHA
cpan Mail::Address
cpan MIME::Base64
cpan Net::DNS
cpan Net::Server
cpan Error
---------------

The another perl module Mail::DKIM which is normally not available in cpan repository. We can download this module from source and installed it in the server.

---------------
wget http://search.cpan.org/CPAN/authors/id/J/JA/JASLONG/Mail-DKIM-0.39.tar.gz
tar -zxvf  Mail-DKIM-0.39.tar.gz
cd Mail-DKIM-0.39
perl Makefile.PL
make
make test
make install
---------------

We have completed the prerequisites for dkimproxy. Now, we would need to install dkim proxy to the server.

Installation:

--------------
wget http://downloads.sourceforge.net/project/dkimproxy/dkimproxy/1.4.1/dkimproxy-1.4.1.tar.gz
tar -zxvf dkimproxy-1.4.1.tar.gz
cd dkimproxy-1.4.1
./configure --prefix=/usr/local/dkimproxy
make install
--------------

Copy the sample startup script to /etc/init.d.

----------
cp sample-dkim-init-script.sh /etc/init.d/dkimproxy
----------

Now, create dkim user dedicated to running dkimproxy.

-----------
useradd -d /usr/local/dkimproxy dkim
-----------

The next step is to create private key and public key pair.

-----------
cd /usr/local/dkimproxy/
openssl genrsa -out private.key 1024
openssl rsa -in private.key -pubout -out public.key
-----------

Now, we would need to add this public key in the DNS zone file of the domain. The public should be present in /usr/local/dkimproxy/public.key.

----------
cat /usr/local/dkimproxy/public.key
----------

We used the selector "selector1" for defining the TXT record.

---------------
selector1._domainkey IN TXT "k=rsa; t=s; p=MHwwDQYJK ... OprwIDAQAB"
---------------

There will be propagation delay of 24 to 48 hours for this DNS change to reflect all over the world. Once the DNS propagation completed, you can verify it by using the following command.

-----------
host -ttxt selector1._domainkey.domainname.com
-----------

We have completed the installation of dkimproxy. Now, we would need to configure dkimproxy to sign the mails by DKIM.

Configuration:

Create a file /usr/local/dkimproxy/etc/dkimproxy_out.conf with the following content.

=====================
# specify what address/port DKIMproxy should listen on
listen    127.0.0.1:10037

# specify what address/port DKIMproxy forwards mail to
relay     127.0.0.1:10038

# specify what domains DKIMproxy can sign for (comma-separated, no spaces)
domain    Domainname.com

# specify what signatures to add
signature dkim(c=relaxed)
signature domainkeys(c=nofws)

# specify location of the private key
keyfile   /usr/local/dkimproxy/private.key

# specify the selector (i.e. the name of the key record put in DNS)
selector  selector1
=====================

Note that we have used "selector1" in DNS zone file for defining TXT record. So, we should use this as a selector.Make sure that private.key and public.key are available in "/usr/local/dkimproxy". In the "domain" field, we can mention what are the domains that will be signed by dkimproxy.

Now, start the dkimproxy and configure it to start at boot:

---------
/etc/init.d/dkimproxy start
chkconfig dkimproxy on
---------

The final step is to configure postfix to use dkimproxy for sending mails.

Postfix configuration:

Add the following content in postfix master configuration file(/etc/postfix/master.cf). Make sure that you have taken the backup of this configuration before editing.

===============
# modify the default submission service to specify a content filter
# and restrict it to local clients and SASL authenticated clients only
#
submission  inet  n     -       n       -       -       smtpd
    -o smtpd_etrn_restrictions=reject
    -o smtpd_sasl_auth_enable=yes
    -o content_filter=dksign:[127.0.0.1]:10037
    -o receive_override_options=no_address_mappings
    -o smtpd_recipient_restrictions=permit_mynetworks,permit_sasl_authenticated,reject

#
# specify the location of the DKIM signing proxy
# Note: we allow "4" simultaneous deliveries here; high-volume sites may
#   want a number higher than 4.
# Note: the smtp_discard_ehlo_keywords option requires Postfix 2.2 or
#   better. Leave it off if your version does not support it.
#
dksign    unix  -       -       n       -       4       smtp
    -o smtp_send_xforward_command=yes
    -o smtp_discard_ehlo_keywords=8bitmime,starttls

#
# service for accepting messages FROM the DKIM signing proxy
#
127.0.0.1:10038 inet  n  -      n       -       10      smtpd
    -o content_filter=
    -o receive_override_options=no_unknown_recipient_checks,no_header_body_checks
    -o smtpd_helo_restrictions=
    -o smtpd_client_restrictions=
    -o smtpd_sender_restrictions=
    -o smtpd_recipient_restrictions=permit_mynetworks,reject
    -o mynetworks=127.0.0.0/8
    -o smtpd_authorized_xforward_hosts=127.0.0.0/8
pickup    fifo  n       -       n       60      1       pickup
    -o content_filter=dksign:[127.0.0.1]:10037
===============

Reload the postfix service.

---------
postfix reload
---------

Dkimproxy is installed in the server. We have used the port 10037 for dkimproxy service.

---------
[root@server ~]# netstat -plan |grep perl|grep 10037
tcp        0      0 127.0.0.1:10037             0.0.0.0:*                   LISTEN      17783/perl         
[root@server ~]#
---------

Verification:

You can verify the dkim signature by sending an email to verifier.port25.com. The authentication result will be send it to the mail account that we mentioned.

mail -v check-auth-username=gmail.com@verifier.port25.com





Thursday, 23 February 2012

Not able to restart Pure-FTPd: 421 Unknown authentication method: extauth:/var/run/ftpd.sock

Not able to restart Pure-FTPd: 421 Unknown authentication method: extauth:/var/run/ftpd.sock

You may get the following error message while restarting Pure-FTPd in cPanel server.

===============
Stopping pure-config.pl: cat: /var/run/pure-ftpd.pid: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Stopping pure-authd:
Starting pure-config.pl: Running: /usr/local/sbin/pure-ftpd -O clf:/var/log/xferlog --daemonize -A -c50 -B -C8 -D -fftp -H -I15 -lextauth:/var/run/ftpd.sock -L10000:8 -m4 -s -U133:022 -u100 -Oxferlog:/usr/local/apache/domlogs/ftpxferlog -k99 -Z -Y1 -JHIGH:MEDIUM:+TLSv1:!SSLv2:+SSLv3
/usr/local/sbin/pure-ftpd: invalid option -- O
421 Unknown authentication method: extauth:/var/run/ftpd.sock
[FAILED]
Starting pure-authd:
===============

How to resolve the issue?

* Ensure that the option " CallUploadScript yes" is commented in Pure-FTPd configuration file "/etc/pure-ftpd.conf ".

===
grep -i CallUploadScript /etc/pure-ftpd.conf
#CallUploadScript yes
===

If it is not commented, then comment it out and try to restart FTP:

===
/etc/init.d/pure-ftpd restart
===

* Ensure that the line " CallUploadScript yes" is not existing in the file "/var/cpanel/conf/pureftpd/main". If it exists, remove that line and save the file.

Tuesday, 21 February 2012

Setting up an SSL website in CentOS/Ubuntu if there is no control panel

This guide will explain how to set up a site over https.

1. Get the required software
~~~~~~~~~~~~~~~~~
For an SSL encrypted web server you will need a few things. Depending on your install you may or may not have OpenSSL and mod_ssl, Apache's interface to OpenSSL.

Use yum to install following, if centos

======================
yum install mod_ssl openssl
======================

Use apt-get to install following, if ubuntu

========================
apt-get install apache2 apache2-common;
========================

Now run following command in ubuntu to enable mod_ssl

================
a2enmod ssl
================

Yum will either tell you they are installed or will install them for you.

2. Generate CSR & purchase SSL
~~~~~~~~~~~~~~~~~~~~~
Get it done as per following KB article.

[ article:832 ]Generating CSR for Customers & Guidelines for SSL installation requests

3. Create /etc/httpd/conf.d/example.com.conf, if centos.

If ubuntu, create /etc/apache2/sites-available/example.com. Now, run following command.

================
a2ensite example.com
================

Now, add following contents in /etc/httpd/conf.d/example.com.conf or /etc/apache2/sites-available/example.com.

==============================
NameVirtualHost 192.168.1.56:443

ServerAdmin admin@example.com
DocumentRoot /var/www/html/example_www/
ServerName server1.example.com
ServerAlias www.example.com
ErrorLog logs/example.com-error_log
CustomLog logs/example.com-access_log common

Allowoverride All


NameVirtualHost 192.168.1.56:443

SSLEngine on
SSLCertificateFile /etc/ssl/example.com.crt
SSLCertificateKeyFile /etc/ssl/example.com.key
SSLCACertificateFile /etc/ssl/example.com.ca

Allowoverride All

ServerAdmin admin@example.com
DocumentRoot /var/www/html/example_com_www/
ServerName server1.example.com
ServerAlias www.example.com
ErrorLog logs/example.com-error_log
CustomLog logs/example.com-access_log common

===============================

Make sure following.

(i) IP 192.168.1.56 is replaced with correct IP address
(ii) example.com is replaced with correct domain name
(iii) document root is /var/www/html/example_com_www/

3. Create /etc/ssl/

4. Save Cert, Key & Intermediate CA as given below.

Cert: /etc/ssl/example.com.crt
Key: /etc/ssl/example.com.key
Intermediate CA: /etc/ssl/example.com.ca

/etc/init.d/httpd restart [ centos]
/etc/init.d/apache2 restart [ubuntu]

5. Access website using https://192.168.1.56:443 and ensure that it is working fine.


Ubuntu reference: https://help.ubuntu.com/10.04/serverguide/C/httpd.html

Monday, 20 February 2012

CloudFlare and its used


CloudFlare: How to speed up my customers blog or website?

You are the owner of a web-hosting company with N number of shared servers.
Customers keeps complaining that the website/blogs are slow or the loading
time of the domain has increased. You are aware about the server that it has
high performance hardware and best software to run the server with 100%
uptime. Still the customers keeps complaining that his/her domain is loading
slow. Perhaps you may loose few customers for this reason.

It is weird that the customers are unaware of the reasons behind the domain
loading slow. But they keep contacting us(the technical team) to know the
reason if the issue is with the server. Even few customers has opened a ticket
saying that the loading time of his domain has increased from 4 seconds to 7
seconds. why? I was cornered for these kind of issues. Even if I inform the
customer that the domain static pages are causing the issue but still they are
not satisfied. I couldn't find an issue in the server but still the issue
persist for the customers. Finally, I have found the solution called
"CloudFlare" which has fulfilled the customer satisfaction.

What is a CloudFlare?

CloudFlare is a CDN service that makes your website faster, safer, and
smarter. In other words, CloudFlare supercharges websites. It performs a
variety of tasks to ensure your visitor will never have to sit down and wait
for your site to load again. It caches resources, it has a new beta feature to
minimize your HTML, CSS and JS if you aren’t already, the Pro version can
preload other pages before you go to them so they appear instantly, it can
manage integrating Google Analytics and has hot-link protection for your
images.


Advantages of CloudFlare.

1. CloudFlare acts as a middle tier, acting as a community that collects
threat information (spammers, bots, etc) and protects your website/blog from
the same threats. CloudFlare keeps your website/blog safe from these attacks
by challenging them with a CAPTCHA system. Also, it blocks all threats and
limit abusive bots and crawlers from wasting your bandwidth and server
resources. The result: CloudFlare-powered websites see a significant
improvement in performance and a decrease in spam and other attacks. With
CloudFlare, you can block spammer's or annoying IP addresses easily with the
control panel.

2. CloudFlare provides an extra caching system. When a visitor comes to your
website/blog, CloudFlare serves them the static contents from a server closest
to your visitor. This improves the load time for your website/blog
significantly because data travel is shorter.  Once your website is a part of
the CloudFlare community, its web traffic is routed through its intelligent
global network. CloudFlare support team automatically optimize the delivery of
your web pages so your visitors get the fastest page load times and best
performance.

3. If your server is down, CloudFlare will serve your visitors its whole cache
(including your pages, posts, etc) so in a way, your website/blog will never
go offline. CloudFlare protects and accelerates any website online. CloudFlare's
system gets faster and smarter as the community of users grows larger. They
have designed the system to scale with the goal in their mind: helping power
and protect the entire Internet.

4. CloudFlare can be used by anyone with a website and their own domain,
regardless of your choice in platform. There is no hardware or software to
install or maintain and you do not need to change any of your site's existing
code. If you are ever unhappy you can turn CloudFlare off as easily as you
turned it on. CloudFlare help to speed up the website by redirecting the traffic
to the nearest node.

5. In general, CloudFlare makes your sites load about 45% faster, uses 60%
less bandwidth and is way more secure.

Script to grep a word inside a tar file

search="123"
tar -tf one.tar | while read filename
do
        if [ -f "${filename}" ]
        then
                mv "${filename}" "${filename}.sav"
        fi
        #
        tar -xf one.tar "${filename}"
        #
        found=`grep -l "${search}" "${filename}"`
        if [ ! "${found}""X" = "X" ]
        then
                echo "Found \"${search}\" in \"${found}\""
                grep "${search}" "${filename}"
                echo ""
        fi
        #
        if [ -f "${filename}.sav" ]
        then
                mv "${filename}.sav" "${filename}"
        fi
done

Sunday, 19 February 2012

Find roundcube version provided by the cPanel and upgrade the roundcube

How to find roundcube version provided by the cPanel?

The roundcube version provided by the cPanel is 0.5.4.
===
-bash-3.2# cat /var/cpanel/roundcube/version
0.5.4.cp11130.1-bash-3.2#
===

cPanel dicument regarding the roundcube
====
http://docs.cpanel.net/twiki/bin/view/AllDocumentation/RoundcubeReadme
====

Upgrade rouncube version

/usr/local/cpanel/bin/update-roundcube --force
cd /usr/local/cpanel/base/3rdparty/
mv roundcube roundcube-backup
wget http://softlayer.dl.sourceforge.net/project/roundcubemail/roundcubemail/0.6/roundcubemail-0.6.tar.gz
tar -zxf roundcubemail-0.6.tar.gz
mv roundcubemail-0.6 roundcube
cp roundcube-backup/config/main.inc.php roundcube/config/
cp roundcube-backup/config/db.inc.php roundcube/config/
chown root:wheel -R roundcube
cd roundcube/config
chown cpanelroundcube:cpanelroundcube db.inc.php
chown cpanelroundcube:cpanelroundcube main.inc.php
echo &gt; /var/cpanel/roundcube/install
chmod +x /var/cpanel/roundcube/install

configure exim + sorbs RBL blacklist

http://www.sorbs.net/mailsystems/exim4.shtml

Exim 4.x is a lot more configurable and hence there is more detail to add...

These entries are normally added to the acl_rcpt ACL in the exim.conf file. The default/example exim configuration should contain an example similar to these.

To deny access, using a normal DNSBL with TXT records.


deny message = Access denied - $sender_host_address\
listed by $dnslist_domain\n$dnslist_text
dnslists = dnsbl.sorbs.net

This will produce a response similar to the following:
550-Access denied - 127.0.0.2 listed by dnsbl.sorbs.net
550 Test entry.
To add an X-Warning header so that users can filter:


warn message = X-Warning: $sender_host_address listed by $dnslist_domain
log_message = Listed by $dnslist_domain
dnslists = dnsbl.sorbs.net Thanks to Josh Rollyson for the info.

=============

ASSP and other mail bounce back number

http://www.dusanvuckovic.com/information-on-bounced-messages-ndr-codes/

These are the ASSP spam filtere bounce back mails code


Please note, that each bounce message is different. Therefore, information relating to

addresses, IP numbers, and domain names listed below will differ from what listed in your

header information. If you have received a bounce message (NDR: Non-Delivery Report) that matches one of the

following messages, find the text that follow below for a complete description.

As you examine an NDR message, look out for a three-digit code, for example, 5.2.1.

If the first number begins with 5.y.z, then it means you are dealing with a permanent error; this message will never be delivered. Occasionally, you get NDRs beginning with 4.y.z, in which case there is hope that email will eventually get through. The place to look for the NDR status code is on the very last line of the report.

NDR codes like 5.5.0 or 4.3.1 may remind you of SMTP errors 550 and 431. Indeed, the 500 series in SMTP has a similar meaning to the 5.y.z codes in an NDR – failure. I expect that you have worked out why there are no 2.y.z NDRs? The reason is that the 2.y.z series mean success, whereas Non-Delivery Reports, by definition, are failures.

NDR Classification As you are beginning to appreciate, these status codes are not random. The first number 4.y.z, or 5.y.z refers to the class of code, for example, 5.y.z is permanent error. Incidentally, we have not seen any status codes beginning with 1.y.z, 3.y.z, or indeed any numbers greater than 5.7.z.

The second number x.1.z means subject. This second digit, 1 in the previous example, gives generic information where as the third digit (z) gives detail. Unfortunately, we have not cracked the complete code for the second digit. However, I have discovered a few useful patterns, for instance, 5.1.x indicates a problem with the email address, as apposed to server or connector problem. In addition, 5.2.x means that the email is too big, somewhere there is a message limit.

Conclusion, it is best to look up your three-digit error in the status code, see NDR table below.

Contents

[hide]

* 1 Most Common Bounce Reasons

* 2 Explanation of various bounce messages

o 2.1 Message rejected

o 2.2 450: Recipient address rejected: Domain not found

o 2.3 500: Recipient address rejected: Recipient mailbox is full

o 2.4 503: Improper use of SMTP command pipelining

o 2.5 540: < email@domain.com >: Recipient address rejected

o 2.6 550: abcdefghijk@excite.com: User unknown

[edit] Most Common Bounce Reasons

* Message rejected: The mailserver used does not match the domain specified

* 450: Recipient address rejected: Domain not found

* 450: unknown[10.123.123.123] : Client host rejected: Too many mails sent!; from=emaillist@domain.com

* 500: Recipient address rejected: Recipient mailbox is full

* 503: Improper use of SMTP command pipelining

* 540: email@domain.com : Recipient address rejected: Your email has been returned because the intended recipient’s email account has been suspended.

* 550: abcdefghijk@excite.com: User unknown

* 550: name.mail.domain.net[10.x.xxx.xx]: Client host rejected: More than X concurrent connections per subnet

* 554: unknown[10.xxx.xxx.xx]: Client host rejected: Access denied

* 554: Client host rejected: cannot find your hostname, [10.xxx.xx.xxx]; from=xxxxx@hotmail.com

* 554: Sender address rejected: Access denied

* 554: Service unavailable; [10.xxx.xx.xxx] blocked using relays.ordb.org, reason: This mail was handled by an open relay – please visit http://ORDB.org/lookup/?host=10.X.X.X

* 554: Relay access denied; from= to= – reject: header Subject: (Email Subject Line)

* Remote host said: 554 Service unavailable; [XXX.XXX.XXX.XXX] blocked using blackholes.excite.com

[edit] Explanation of various bounce messages

[edit] Message rejected

The mailserver used does not match the domain specified

This message was not delivered because the headers indicate that it is coming from an email service other than the one indicated by the IP address. It is a common practice of Spammers to forge message headers in this manner, therefore this type of message will not be delivered.

For example, a message with a return address of 1user@domainname.com which was actually sent through a service with an IP address which does not match domainname.com will be rejected for this reason.

[edit] 450: Recipient address rejected: Domain not found

450 unknown[10.123.123.123]: Client host rejected: Too many mails sent!; from=emaillist@domain.com

To protect email system from being flooded by email list administrators, or in some cases by “spammers,” ISP’s have instituted “rules” to gate incoming email to their systems.

These rules are mostly based on common industry practices as to how to send large amounts of email without causing potential harm to the recipient’s mail server.

Unfortunately, from time to time, we are forced to “soft bounce messages because the mailing it was a part of exceeded one or more of the rules for incoming email. However, a “soft bounce” means that we will deliver the email in question, although it will result in a short delay in receipt.

The mail servers that were responsible for delivering the bounced message may have been blocked due to a high number of concurrent connections. This type of abuse is usually indicative of a “spammer” trying to send unsolicited commercial emails. Therefore, the message was blocked along with all other messages from that mail server. This decision is made automatically by computer programs and do result in a significant percentage of false positives. Since the email provider in question has been added to one or more block list(s), the bounced message will continue to be generated.

[edit] 500: Recipient address rejected: Recipient mailbox is full

The email address in question is over its storage limit. For example:

* Excite mail accounts are currently set up with 125MBs of storage space, or 10,000 emails.

* The storage limit for a free Yahoo! Mail account is 1GB.

*

When an email account goes over the quota, emails sent to that account will be

“bounced” back to the sender until the space has been cleared. Unfortunately, we have no

way of knowing if the member in question is aware of the status of their storage space, or

the frequency with which they check their quota.

At ACOR, since many of our subscribers go away for treatment for long periods of time, we receive a lot of those error messages.

[edit] 503: Improper use of SMTP command pipelining

The message was sent in a non-conventional, non-standard way. You should have the

sender of this email contact us if they have further questions.

[edit] 540: < email@domain.com >: Recipient address rejected

Your email has been returned because the intended recipient’s email account has been suspended. The account must be

re-activated to receive incoming messages.

As noted often in the Free Email Services Terms of Service, email accounts that have not been accessed

for more than xxxx days may be deactivated.

If you are an Excite Member, you can reactivate your account by simply signing in to your

Email account, where you will be prompted with a message asking if you would like to

reactivate your email account. After agreeing to do so, your email address will automatically

be reactivated. Please note it may take up to two hours for you to begin receiving new

email messages after you’ve reactivated the account, and remember to access your email

at least once every 60 days to prevent this from occurring in the future.

If you received a “bounced” message to one of the Free Email Services Providers email

user, we suggest that you find an alternate mean of communicating with them to let them

know their email account is now inactive, and that they need to access their Inbox

to reactive their email account.

[edit] 550: abcdefghijk@excite.com: User unknown

If the Excite email account in question is generating “bounced” message that state “User

Unknown” when an individual attempts to send email to it, it could mean that the email

account was not activated after the user registered for their Excite Member account.

For the Excite email account to have been activated, the Member would need to have been

signed into their Excite Member account. From there, they would have been prompted to

agree with the Excite email system’s Terms of Service and Privacy Policy by selecting the

“Accept and Continue” option. Once this was complete, the Member would need to have

signed into the Excite email account to fully activate it. Furthermore, the account will not

start receiving email until 1 hour after it has been fully activated.

If you are sure that the Excite email account in question has been fully activated, and the

account in question is still generating “User Unknown” bounced messages, please contact

your email administrator, and ask them to contact us at emailadmin@cs.excite.com for

further assistance.

550: name.mail.domain.net[10.x.xxx.xx]: Client host rejected: More than 20 concurrent connections per subnet

It appears that the mail servers that were responsible for delivering the message to us were

temporarily blocked due to a high number of concurrent connections. This type of abuse is

usually indicative of a “spammer” trying to send unsolicited commercial emails. Therefore,

the message was blocked along with all other messages from that mail server at that time.

However, it is likely that the block was subsequently removed.

554: unknown[10.xxx.xxx.xx]: Client host rejected: Access denied

554: Sender address rejected: Access denied

Your message is being blocked by our site because it either had characteristics similar to

“spam” (unsolicited commercial email), or you’re sending your message from an Internet

Service Provider (ISP) or email provider who has been identified as having allowed spam to

be generated from their facilities. For the protection of our members, we do not deliver

bulk, unsolicited emails to Excite email accounts.

For example, it is possible that the subject line of the message in question may have been

identified by our email servers as unsolicited commercial mail (AKA: Spam) and thus was

returned. We ask that you retry sending your message with a different subject line. Please

ensure that the subject line of the message does not contain more than 15 identical

characters.

For instance, if a subject line contains 15 identical consecutive characters, such as 15 “a”s

or 15 “!”s it may be rejected on our end.

However, if your ISP or email provider has been added to our block list, your email message

to @excite.com will continue to be rejected or a bounced message will continue to be

generated. If this is the case, please contact your email administrator, and ask them to

contact us for further assistance.

554: Sender address rejected: Access denied

- This address is listed on our “black list” of email addresses, or is on the black list of one of

the spam filter lists we use to lessen the amount of Spam our users receive. You should

have the owner of this address contact us if they have questions.

554: Service unavailable; [10.xxx.xx.xxx] blocked using relays.ordb.org, reason: This mail was handled by an open relay – please visit http://ORDB.org/lookup/?host=10.X.X.X

The message in question was blocked because it came from a domain or IP address that is

currently listed with one of our Spam filters. These filters are utilized to help prevent

excessive spamming to our email providers. If your domain or IP address is listed with any

of the four Spam filters we currently use, your message will not be delivered.

If you believe that you have been unfairly added to any or all of these particular lists,

please contact the website in question:

* Ordb (relays.ordb.org)

* Spamcop (bl.spamcop.net)

* Osirusoft (socks.relays.osirusoft.com)

* Wirehub (blackholes.wirehub.net)

* Spamhaus

554: Client host rejected: cannot find your hostname, [10.xxx.xx.xxx]; from=xxxxx@hotmail.com

554: Relay access denied; from=email@domain.com to=email@anotherdomain.com

This error means that the person sending the email was not authorized to use the email

server (SMTP) server to send email. They should contact their ISP or email provider.

reject: header Subject: (Email Subject Line Here)

This subject line is on our “black list” of subject lines, or is on the black list of one of the

spam filter lists we use to lessen the amount of Spam our users receive. You should have

the sender of this email contact us if they have questions, or ask them, to change the

subject line, which unfortunately appears to have been used as the subject of a “spam” message at some time.

Remote host said: 554 Service unavailable; [XXX.XXX.XXX.XXX] blocked using blackholes.excite.com

We have recently received a large number of abuse complaints regarding your account (and/or your ISP). As a result, we have bounced your email message back to you.

This means your IP number (represented above by XXX.XXX.XXX.XXX) has been blocked due to spamming activity by you, or someone using the same IP address or IP address range from your ISP. You may wish to let your ISP know of the situation. While this blocks are usually temporary, if we see repeated activity from this IP address or IP address range, it may be permanently blocked from sending email to our mail system

We hope this answers your questions about bounced email to our mail system.

Standard SMTP Reply Codes:

Code Description

211 System status, or system help reply.

214 Help message.

220 Domain service ready.

Ready to start TLS.

221 Domain service closing transmission channel.

250 OK, queuing for node node started.

Requested mail action okay, completed.

251 OK, no messages waiting for node node.

User not local, will forward to forwardpath.

252 OK, pending messages for node node started.

Cannot VRFY user (e.g., info is not local), but will take message for this user and attempt delivery.

253 OK, messages pending messages for node node started.

354 Start mail input; end with ..

355 Octet-offset is the transaction offset.

421 Domain service not available, closing transmission channel.

432 A password transition is needed.

450 Requested mail action not taken: mailbox unavailable.

ATRN request refused.

451 Requested action aborted: local error in processing.

Unable to process ATRN request now

452 Requested action not taken: insufficient system storage.

453 You have no mail.

454 TLS not available due to temporary reason.

Encryption required for requested authentication mechanism.

458 Unable to queue messages for node node.

459 Node node not allowed: reason.

500 Command not recognized: command.

Syntax error.

501 Syntax error, no parameters allowed.

502 Command not implemented.

503 Bad sequence of commands.

504 Command parameter not implemented.

521 Machine does not accept mail.

530 Must issue a STARTTLS command first.

Encryption required for requested authentication mechanism.

534 Authentication mechanism is too weak.

538 Encryption required for requested authentication mechanism.

550 Requested action not taken: mailbox unavailable.

551 User not local; please try forwardpath.

552 Requested mail action aborted: exceeded storage allocation.

553 Requested action not taken: mailbox name not allowed.

554 Transaction failed.

NDR Code Explanation of Non-Delivery Report error codes from Email Servers

4.2.2 The recipient has exceeded their mailbox limit. It could also be that the delivery directory on the Virtual server has exceeded its limit.

4.3.1 Not enough disk space on the delivery server. Microsoft say this NDR maybe reported as out-of-memory error.

4.3.2 Classic temporary problem, the Administrator has frozen the queue.

4.4.1 Intermittent network connection. The server has not yet responded. Classic temporary problem. If it persists, you will also a 5.4.x status code error.

4.4.2 The server started to deliver the message but then the connection was broken.

4.4.6 Too many hops. Most likely, the message is looping.

4.4.7 Problem with a timeout. Check receiving server connectors.

4.4.9 A DNS problem. Check your smart host setting on the SMTP connector. For example, check correct SMTP format. Also, use square brackets in the IP address [197.89.1.4] You can get this same NDR error if you have been deleting routing groups.

4.6.5 Multi-language situation. Your server does not have the correct language code page installed.

5.0.0 SMTP 500 reply code means an unrecognised command. You get this NDR when you make a typing mistake when you manually try to send email via telnet.

More likely, a routing group error, no routing connector, or no suitable address space in the connector. (Try adding * in the address space)

This status code is a general error message in Exchange 2000. In fact Microsoft introduced a service pack to make sure now get a more specific code.

5.1.x Problem with email address.

5.1.0 Often seen with contacts. Check the recipient address.

5.1.1 Another problem with the recipient address. Possibly the user was moved to another server in Active Directory. Maybe an Outlook client replied to a message while offline.

5.1.2

SMTP; 550 Host unknown. An error is triggered when the host name can’t be found. For example, when trying to send an email to bob@ nonexistantdomain.com.

5.1.3

Another problem with contacts. Address field maybe empty. Check the address information.

5.1.4

Two objects have the same address, which confuses the categorizer.

5.1.5

Destination mailbox address invalid.

5.1.6

Problem with homeMDB or msExchHomeServerName – check how many users are affected. Sometimes running RUS (Recipient Update Service) cures this problem. Mailbox may have moved.

5.1.7

Problem with senders mail attribute, check properties sheet in ADUC.

5.2.x

NDR caused by a problem with the large size of the email.

5.2.1

The message is too large. Else it could be a permissions problem. Check the recipient’s mailbox.

5.2.2

Sadly, the recipient has exceeded their mailbox limit.

5.2.3

Recipient cannot receive messages this big. Server or connector limit exceeded.

5.2.4

Most likely, a distribution list or group is trying to send an email. Check where the expansion server is situated.

5.3.0

Problem with MTA, maybe someone has been editing the registry to disable the MTA / Store driver.

5.3.1

Mail system full. Possibly a Standard edition of Exchange reached the 16 GB limit.

5.3.2

System not accepting network messages. Look outside Exchange for a connectivity problem.

5.3.3

Remote server has insufficient disk space to hold email. Check SMTP log.

5.3.4

Message too big. Check limits, System Policy, connector, virtual server.

5.3.5

Multiple Virtual Servers are using the same IP address and port. See Microsoft TechNet article: 321721 Sharing SMTP. Email probably looping.

5.4.0

DNS Problem. Check the Smart host, or check your DNS. It means that there is no DNS server that can resolve this email address. Could be Virtual Server SMTP address.

5.4.1

No answer from host. Not Exchange’s fault check connections.

5.4.2

Bad connection.

5.4.3

Routing server failure. No available route.

5.4.4

Cannot find the next hop, check the Routing Group Connector. Perhaps you have Exchange servers in different Routing Groups, but no connector.

5.4.6

Tricky looping problem, a contact has the same email address as an Active Directory user. One user is probably using an Alternate Recipient with the same email address as a contact.

5.4.7

Delivery time-out. Message is taking too long to be delivered.

5.4.8

Microsoft advise, check your recipient policy. SMTP address should be cp.com.

NOT server.cp.com.

5.5.0

Underlying SMTP 500 error. Our server tried ehlo, the recipient’s server did not understand and returned a 550 or 500 error. Set up SMTP logging.

5.5.2

Possibly the disk holding the operating system is full. Or could be a syntax error if you are executing SMTP from a telnet shell.

5.5.3

More than 5,000 recipients. Check the Global Settings, Message Delivery properties.

5.5.5

Wrong protocol version

5.6.3

More than 250 attachments.

5.7.1

Permissions problem. For some reason the sender is not allowed to email this account. Perhaps an anonymous user is trying to send mail to a distribution list.

Check SMTP

Virtual Server Access Tab. Try checking this box: Allow computers which successfully authenticate to relay

User may have a manually created email address that does not match a

System Policy.

5.7.2

Distribution list cannot expand and so is unable to deliver its messages.

5.7.3

Check external IP address of ISA server. Make sure it matches the SMTP publishing rule.

5.7.4

Extra security features not supported. Check delivery server settings

5.7.5

Cryptographic failure. Try a plain message with encryption.

5.7.6

Certificate problem, encryption level maybe to high.

5.7.7

Message integrity problem.

Maldet scanner for cPanel




Installation
=========
wget http://www.rfxn.com/downloads/maldetect-current.tar.gz

tar -xzvf maldetect-current.tar.gz


cd maldetect-*


sh install.sh


After running the install script , the installation will complete with in seconds and you will be provided with successful installation output, in this information some of the main configuration and usage related information provided is   below :installation completed to /usr/local/maldetect

config file: /usr/local/maldetect/conf.maldet
exec file: /usr/local/maldetect/maldet
exec link: /usr/local/sbin/maldet
exec link: /usr/local/sbin/lmd
cron.daily: /etc/cron.daily/maldet


As you can see from above output the main configuration file for malware detect is located at below path :
/usr/local/maldetect/conf.maldet

The main cron is located at /etc/cron.daily/maldet
The configuration file is fully commented so you should be able to make out most options but lets take a moment to review the more important ones anyways.

email_alert
This is a top level toggle for the e-mail alert system, this must be turned on if you want to receive alerts.

email_addr
This is a comma spaced list of e-mail addresses that should receive alerts.

quar_hits
This tells LMD that it should move malware content into the quarantine path and strip it of all permissions. Files are fully restorable to original path, owner and permission using the –restore FILE option.

quar_clean
This tells LMD that it should try to clean malware that it has cleaner rules for, at the moment base64_decode and gzinflate file injection strings can be cleaned. Files that are cleaned are automatically restored to original path, owner and permission.

quar_susp
Using this option allows LMD to suspend a user account that malware is found residing under. On CPanel systems this will pass the user to /scripts/suspendacct and add a comment with the maldet report command to the report that caused the users suspension (e.g: maldet –report SCANID). On non-cpanel systems, the users shell will be set to /bin/false.

quar_susp_minuid
This is the minimum user id that will be evaluated for suspension, the default should be fine on most systems.

Usage & Manual Scan
=================
If we wanted to scan all user public_html paths under /home*/ this can be done with:
maldet –scan-all /home?/?/public_html

If you wanted to scan the same path but scope it to content that has been created/modified in the last 5 days you would run:
maldet –scan-recent /home?/?/public_html 5

If you performed a scan but forget to turn on the quarantine option, you could quarantine all malware results from a previous scan with:
maldet –quarantine SCANID

Similarly to the above, if you wanted to attempt a clean on all malware results from a previous scan that did not have the feature enabled, you would do so with:
maldet –clean SCANID





Friday, 17 February 2012

cPanel max emails per hour, max emails per domain

This Post will help you in setting Max Emails allowed per hour in various Levels:

To set the Value Server Wide:

You can set the value in the following file in the case of cPanel:

=====
/var/cpanel/maxemailsperhour
=====

You can set this limit at the user level by editing the following file:

 =====
 /var/cpanel/maxemailsperdomain
 =====

Under the above mentioned location, you can create a file name which matches the domain name and you can set the limit in that file. You can just write the value ( I mean the number of emails)


If you update the above mentioned files, you need to execute the following script to update the changes.

========

/scripts/build_maxemails_config
 ========

Have a Happy Emailing :) 

Thursday, 16 February 2012

Site prompting for username and password when accessing in browser

Prompt for Username and password when accessing the site in Plesk:
============================================

Issue : We may get a pop-up prompting for username and password when we access a site in the browser.

Cause : The permission for the User will be wrong.

Resolution : Please check whether 'Plesk Domain user, Plesk IIS user and Plesk IIS WP user' is allowed for the domain. If not please add the user for this domain. You can add permission as follows.

Steps:
======
1. Open IIS Manager.

2. Select the domain name in the left side under "websites".

3. Right click on the domain name and click permissions.

4. In the first tab called 'security', check whether all the users are available.

5. If any of the user is not there, then add user as follows.
    * Click 'add' under security tab.
    * Click 'Advaced..' in the 'Select Users or Groups' window.
    * Now click 'Find Now'.
    * Select the user which you want to add (Plesk Domain user/Please IIS user/Plesk IIS WP user)
    * Click 'ok' in all the tabs to add the user.

6. Now access the domain in the browser.

Note :
-----
Plesk Domain user - Username
Plesk IIS user   - IUSR_Username
Plesk IIS WP user - IWPD_Username

The issue is fixed :)

Have a nice day :)

Wednesday, 15 February 2012

Command to check the opened/closed ports in a server

You can check with the following command to see the opened/closed ports of a server:

======
# nmap -P0 -T4 -sV -p-
Server_IP_Address

Starting Nmap 5.00 ( http://nmap.org ) at 2012-02-16 06:28 IST
Connect Scan Timing: About 90.53% done; ETC: 06:47 (0:01:47 remaining)
Interesting ports on xxx.xxxx.xx (Server_IP_Address):

Not shown: 65480 filtered ports, 41 closed ports
PORT STATE SERVICE VERSION
53/tcp open domain
110/tcp open pop3 Dovecot pop3d
143/tcp open imap Dovecot imapd
993/tcp open ssl/imap Dovecot imapd
995/tcp open ssl/pop3 Dovecot pop3d
2077/tcp open unknown
2078/tcp open ssl/unknown
2082/tcp open unknown
2083/tcp open ssl/unknown
2086/tcp open unknown
2087/tcp open ssl/unknown
2095/tcp open unknown
2096/tcp open ssl/unknown
8080/tcp open http Apache Tomcat/Coyote JSP engine 1.1
8 services unrecognized despite returning data.
======


To troubleshoot DDOS

This summary is not available. Please click here to view the post.

Script to check Virt VPS load (and other commands)

This summary is not available. Please click here to view the post.

Tuesday, 14 February 2012

Script to Make a backup of the current database and restore DB from the available backup of all the database owned by a particular user in cPanel

You can make use of the following script to generate a backup of all the databases and also restoring the DB from the available backup in cPanel owned by a particular user.

=============
#!/bin/bash
cd /var/lib/mysql
ls -al | grep username | awk {'print$9'} > dblist
for i in `cat dblist`
do
mysqldump $i > $i.sql;
mv $i.sql /home/username
done
cp /backup/cpbackup/monthly/username/mysql/yogabook_*.sql /var/lib/mysql
for i in `cat dblist`
do
mysql $i < $i.sql;
done

=============

Have a Great Day :) :)

Wordpress index hacked page recovery

Wordpress index page hacked by hackers. You need to replace the new index page in the current wordpress directory.


May of my customers gave a complain that the wordpress index.php files are hacked by the hackers. They are placing their own logo or hack message in the wordpress. How can you fix the issue. Simply you need to replace the index page with the wordpress default index pages.

If you are familiarized with the cPanel file manager option, then kindly follow the steps below to replace the index files of wordpress.
  1. Please access your cPanel, and open your File Manager.
  2. Navigate to the Document Root of your WordPress installation. (usually public_html). If this is in regards to an addon domain, you will find this in a separate folder inside of public_html which is named after the domain.
  3. Locate the file called index.php, and open it for editing using the toolbar options or right-click menu (Edit or Code Editor).
  4. Select all and delete the contents of this file.
  5. Copy and paste the code found in the link into this file to replace the original WordPress code.
  6. Save the changes to this file.
  7. You may now reload your website. You may need to refresh your page or clear your browser cache if you do not immediately see the changes.
  8. This fixes the defacement of the home page, but you will still need to modify one additional file to repair your admin section.
  9. From where you are in the File Manager from the previous step, look for the wp-admin folder and enter it.
  10. Locate the index.php file and open it for editing using the toolbar or right click menu (Edit or Code Editor)
  11. Select all and delete all contents of this file.
  12. Copy and paste the code found in the link into your file.
  13. Save the changes to this file
  14. You should now be able to access your admin area as well as load your site.


FIX
Upload your original theme that you are using index.php to fix the site.
They also delete the admin user #1 from the mysql database.
Use phpmyadmin in your cpanel to access your database.
Select your database on the left sidebar
Find wp_users and select browse
Note that user 1 is missing...thats what the hacker deleted
My easy fix is to take another id 2 or 3 etc and click edit
Change id value to 1
Change user_login value to your username
user_pass row set function to MD5 and value to your password
Change user_name value to your username
Click Go
You are now a little less frustrated because you can now log into your admin panel but are ticked off that your site has been hacked twice in the last week. Your hosting provider can not stop the attacks and tells you to upgrade to the latest version of wordpress which you are already running.




Monday, 13 February 2012

Common issues with Wordpress and their Fixes

The Wordpress website will not be loading fine.

Check the following factors to resolve the issue.

1. If you are getting a database connection problem, then go to wp-config.php file and gather the information about the database settings and the database user login details.

Cross check whether the login credentials are working fine or not.

2. Secondly ensure that you have given the appropriate privileges to the assigned database user.

3. You can check whether the SiteURL defined for the Wordpress is set correctly. You can edit the SiteURL by accessing the Wordpress admin panel. You can also change it by using MySQL command prompt.

>> Use the following command to change the SiteURL:

    
update wp_options set option_value = 'http://example.com' where option_name = 'siteurl';

4. Regardless of the above mentioned reasons, the site will not be loading if some of the Plugins or Themes of the Wordpress are not compatible with the current version of the Wordpress installed.
In this case, you can disable that particular Plugin/Theme to resolve the issue. :) 

Have a Nice Day :)

Wordpress wp-admin index page


Wordpress wp-admin index.php page.


<?php
/**
 * Dashboard Administration Panel
 *
 * @package WordPress
 * @subpackage Administration
 */

/** Load WordPress Bootstrap */
require_once('./admin.php');

/** Load WordPress dashboard API */
require_once(ABSPATH . 'wp-admin/includes/dashboard.php');

wp_dashboard_setup();

wp_enqueue_script( 'dashboard' );
wp_enqueue_script( 'plugin-install' );
wp_enqueue_script( 'media-upload' );
wp_admin_css( 'dashboard' );
wp_admin_css( 'plugin-install' );
add_thickbox();

$title = __('Dashboard');
$parent_file = 'index.php';

if ( is_user_admin() )
 add_screen_option('layout_columns', array('max' => 4, 'default' => 1) );
else
 add_screen_option('layout_columns', array('max' => 4, 'default' => 2) );

add_contextual_help($current_screen,

 '<p>' . __( 'Welcome to your WordPress Dashboard! You will find helpful tips in the Help tab of each screen to assist you as you get to know the application.' ) . '</p>' .
 '<p>' . __( 'The Admin Bar at the top, new in 3.1, provides quick access to common tasks when you are viewing your site.' ) . '</p>' .
 '<p>' . __( 'The left-hand navigation menu provides links to the administration screens in your WordPress application. You can expand or collapse navigation sections by clicking on the arrow that appears on the right side of each navigation item when you hover over it. You can also minimize the navigation menu to a narrow icon strip by clicking on the faint separator lines between the Dashboard and Posts sections, or between Comments and Appearance; when minimized, the submenu items will be displayed on hover.' ) . '</p>' .
 '<p>' . __( 'You can configure your dashboard by choosing which boxes, or modules, to display in the work area, how many columns to display them in, and where each box should be placed. You can hide/show boxes and select the number of columns in the Screen Options tab. To rearrange the boxes, drag and drop by clicking on the title bar of the selected box and releasing when you see a gray dotted-line rectangle appear in the location you want to place the box. You can also expand or collapse each box by clicking once on the title bar of the box. In addition, some boxes are configurable, and will show a &#8220;Configure&#8221; link in the title bar when you hover over it.' ) . '</p>' .
 '<p>' . __( 'The boxes on your Dashboard screen are:' ) . '</p>' .
 '<p>' . __( '<strong>Right Now</strong> - Displays a summary of the content on your site and identifies which theme and version of WordPress you are using.' ) . '</p>' .
 '<p>' . __( '<strong>Recent Comments</strong> - Shows the most recent comments on your posts (configurable, up to 30) and allows you to moderate them.' ) . '</p>' .
 '<p>' . __( '<strong>Incoming Links</strong> - Shows links to your site found by Google Blog Search.' ) . '</p>' .
 '<p>' . __( '<strong>QuickPress</strong> - Allows you to create a new post and either publish it or save it as a draft.' ) . '</p>' .
 '<p>' . __( '<strong>Recent Drafts</strong> - Displays links to the 5 most recent draft posts you&#8217;ve started.' ) . '</p>' .
 '<p>' . __( '<strong>WordPress Development Blog</strong> - Come here for the latest scoop.' ) . '</p>' .
 '<p>' . __( '<strong>Other WordPress News</strong> - Shows the feed from <a href="http://planet.wordpress.org" target="_blank">WordPress Planet</a>. You can configure it to show a different feed of your choosing.' ) . '</p>' .
 '<p>' . __( '<strong>Plugins</strong> - Features the most popular, newest, and recently updated plugins from the WordPress.org Plugin Directory.' ) . '</p>' .
 '<p><strong>' . __( 'For more information:' ) . '</strong></p>' .
 '<p>' . __( '<a href="http://codex.wordpress.org/Dashboard_SubPanel" target="_blank">Documentation on Dashboard</a>' ) . '</p>' .
 '<p>' . __( '<a href="http://wordpress.org/support/" target="_blank">Support Forums</a>' ) . '</p>'
);

include (ABSPATH . 'wp-admin/admin-header.php');

$today = current_time('mysql', 1);
?>

<div class="wrap">
<?php screen_icon(); ?>
<h2><?php echo esc_html( $title ); ?></h2>

<div id="dashboard-widgets-wrap">

<?php wp_dashboard(); ?>

<div class="clear"></div>
</div><!-- dashboard-widgets-wrap -->

</div><!-- wrap -->

<?php require(ABSPATH . 'wp-admin/admin-footer.php'); ?>

Wordpress index file


Wordpress index file. "index.php". This file can be used if the index hacking has done in the wordpress.



<?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');
?>

Sunday, 12 February 2012

Changing the nameserver from the Godaddy Admin panel

Please change the registered nameservers of the domain from the Godaddy admin panel, by using the below mentioned steps:

1. Log in to your GoDaddy.com account

2. Click on the "My Account" tab

3. Select the domain you want to adjust the Nameservers for

4. From the toolbar, select "Nameservers" > "Set Nameservers"

5. In the popup window, select "I have specific nameservers for my domains"

6. Enter "NS1.EXAMPLE.COM" in the nameserver 1 field

7. Enter "NS2.EXAMPLE.COM" in the nameserver 2 field

8. Save changes.

Have a Nice Day :)

Adding nameservers to your server

In rare cases, the nameserver entries will be missing in your server.

In such cases, you can do the following to add the nameservers in your server.

1. Add a DNS zone by adding the nameserver name.

2. Assign a A record for that nameserver.

3. From the SSH as root, in the case of cPanel, you can add the entry in the file mentioned below.

===========
 /var/cpanel/nameserverips.yaml
===========

The syntax will be as follows in the above mentioned file.

nameserver name : IP : ....

You can add the appropriate entry and then Restart cPanel to make the entry active.

Once you do this, the newly added nameservers will be resolving fine. :)

Have a Nice Day....


How to Create a Catch-all email address in cPanel

You can create a catch-all email address in cPanel by following the below mentioned steps.

Sign in to cPanel and follow these steps:

1) Click Default Address under Mail.

2) Select Forward to email address.

3) Enter your desired catch-all email address into the Forward to email address: box.

4) Click Change.

5) You will then get a confirmation that your catch-all address has been setup.

Have a Great Day :)


Steps to obtain Trace route result

The steps for obtaining 'traceroute' is given below.
---------------
*Windows: Click Start, Run, type 'cmd' and press enter.
Type 'tracert domain.com' and press enter.
Right click in the prompt, click Mark, highlight the entire output of the trace route and press enter.

*Linux: Open a shell prompt.
Type 'traceroute domain.com' and press enter.

*Mac OS: Double click the hard drive icon.
From your hard drive, open the Applications folder.
Open the Utilities folder.
Double-click 'Terminal'.
Type the command" traceroute 'domain.com'.
-----------------------

***(Note: replace 'domain.com' with the actual domain name to which you want to trace).

You can find the traceroute results from thirdparty sites like the following:

========
 http://tools.pingdom.com/ping/
========

You can make use of this option in cases where your public IP address is being blocked by the server firewall and as a result you will not be able to obtain the traceroute results from your local machine.

Have a Nice Day :)


How to Clear Browser Cache

Each time you access a web page via web browser, the browser caches (i.e., stores) it. This makes the browser to act in a fast manner by optimizing the time to retrieve data each and every time.

It is better to clear the browser cache periodically, in order to make your browser functionality more efficient.

A cookie typically store user-specific information such as selections in a form, shopping cart contents, or authentication data. Browsers will normally clear cookies that reach a certain age, but clearing them manually may solve problems with web sites or your browser.

 Following are the Easy Steps to Clear your Browser Cache:

Internet Explorer 8 and above


 From the Safety  menu in the upper right, Click Delete Browser History.

 Deselect Preserve Favorites website data, and select Temporary internet files, cookies and history.

 Click Delete.

Internet Explorer 7

 From the Tools menu in the upper right, select Internet options.

 Under "Browsing history", click Delete.

 To delete your cache, click Delete Files.

 To delete your history, Click Delete History.

 Click Close, and then click on OK to exit.

 

Firefox 3.5 and above for Windows

  1. From the Tools menu, select Clear Recent History.
  2. From the Time Range drop-down menu, select the desired range; to clear your entire cache, select Everything.
  3. You can choose the specific optioon by clicking the down arrow next to "Details". Click Clear Now.

Firefox 3 for Windows

  1. From the Tools menu, select Clear Recent History and then select the items you want to delete.
  2. Click Clear Recent History.

Chrome

  1. In the browser bar, enter: chrome://settings/clearBrowserData
  2. Select the items you want to clear
    You can choose the period of time for which you want to clear cached information from the drop-down menu. To clear your entire cache, select the beginning of time.
  3. Click Clear Browsing Data.

Safari

  1. From the Safari menu, select Reset Safari.
  2. From the menu, select the items you want to reset, and then click Reset. As of Safari 5.1, Remove all Website data covers both cookies and cache.

Firefox 3.5 and above for Mac OS X

  1. From the Tools menu, select Clear Recent History.
  2. From the Time range drop-down menu, select the desired range; to clear your entire cache, select Everything.
  3. Click the down arrow next to "Details" to choose which elements to clear. Click Clear Now.

Firefox 3 for Mac OS X

  1. In Firefox, from the Tools menu, select Clear Recent History.
  2. Select the elements you want to clear and then click Clear Private Data now.

Mobile Safari for iPhone OS (iPhone, iPod touch, iPad)

To clear cache and cookies:
  1. From the home screen, tap Settings, and then tap Safari.
  2. At the bottom of Safari's settings screen, tap the buttons for Clear Cookies and Clear Cache.
To clear history:
  1. From the home screen, tap Safari.
  2. At the bottom of the screen, tap the Bookmarks icon.
  3. In the lower left, tap Clear.
  4. Tap Clear History.

Android

To clear cache, cookies, or history:
  1. Start your browser.
  2. Tap Menu, and then tap More.
  3. Select Settings.
  4. Under "Privacy settings", select Clear Cache, Clear History or Clear All Cookie Data as appropriate, and then tap OK to accept.