The album contains the following tracks:

1. The Recession (Intro)
2. Welcome Back
3. By The Way
4. Crazy World
5. What They Want
6. Amazin’
7. Hustlaz Ambition
8. Who Dat
9. Don’t You Know
10. Circulate
11. Word Play
12. Vacation
13. Everything (Feat. Anthony Hamilton And Lil Boosie)
14. Takin’ It There (Feat. Trey Songz)
15. Don’t Do It
16. Put On (Feat. Kanye West)
17. Get Allot
18. My President (Feat. Nas)

Usually when you are trying to do something on linux and have no ideea you usually google it. I was doing it myself recently when i had to put up a new web server with apache 2 and i just decided to change from the standard mod php to fastcgi spawned php and from regular prefork MPM to the worker one.
Well trust me i’ve been crawling all the net for several days and i found so many advices and tips and mini howtos, that in the end all the info got so mixed in my head i was unable to figure it out.
So i started out step-by-step and reading all the readme files and docs of apache and php alike as well as fcgi specs.
I’m publishing this just for the reason of being usefull to other persons like me, rather than just have “YET ANOTHER” howto alongside miriads of others.

But let’s just start

You may or may not know that PHP is considered not to be thread-safe therefore not suitable to be run in multi-threaded envs like apache with worker-mpm. Well i’ve decided to test on my own and see if those statements are true and if i manage to get to see the “PHP has encountered an access violation at memory_address” error. I wouldnt like to dissapoint people at neosmart.net[http://neosmart.net/blog/2008/dont-believe-the-lies-php-isnt-thread-safe-yet/] and i wouldnt want by comments to earn a collective cockpunch but my experience with fcgi’d PHP5 under apache+worker=mpm is the best possible one.

I’m not covering all the apache2 initiald eploy, and even if you didnt installed any of htem yet the command i’ll issue will check dependencies and ask you to install all the other pre-requisites. Pay attention to the fact that when you are trying to install the apache2-mpm-worker package your Debian will want to uninstall the libapache2-mod-php5 one. That’s because the PHP5 module is not compatible with the multithreaded version of apache. It only owrk with standard prefork MPM.

So we are goign to use worker but there’s no more php5 module. Worry not as we will run it as cgi within fastcgi thus freeing apache itself that will only serve static content as images, html files, css etc, while all dynamic php content will be served by php itself.

gw1-livent:~# apt-get install apache2-mpm-worker libapache2-mod-fcgid
Reading package lists… Done
Building dependency tree… Done
The following extra packages will be installed:
apache2.2-common
The following packages will be REMOVED:
apache2-mpm-prefork libapache2-mod-php5
The following NEW packages will be installed:
apache2-mpm-worker libapache2-mod-fcgid
The following packages will be upgraded:
apache2.2-common
1 upgraded, 2 newly installed, 2 to remove and 75 not upgraded.
Need to get 1424kB of archives.
After unpacking 5349kB disk space will be freed.
Do you want to continue [Y/n]?

Just pressing enter will continue with the installation of the necessary packages.
The fastcgi module will be enabled at install time. You should see something like

Setting up libapache2-mod-fcgid (1.10-2) …
Module fcgid installed; run /etc/init.d/apache2 force-reload to enable.

However, if you dont you will need to enable it manual using:

gw1-livent:~# a2enmod fcgid

And you should see the same message “Module fcgid installed; run /etc/init.d/apache2 force-reload to enable.”
Make sure to edit you /etc/apache/mods-enabled/fcgid.conf so it looks like:

<IfModule mod_fcgid.c>
AddHandler fcgid-script .fcgi
SocketPath /var/lib/apache2/fcgid/sock
IPCConnectTimeout 20
</IfModule>

Now that we are done with the fastcgi part we need to reinstall PHP5 which was previously uninstalled.

gw1-livent:~# apt-get install php5-cgi php5-curl php5-gd php5-ldap php5-mysql php5-sqlite php5-xsl

(Feel free to browse the php5 packages and modify the line above to suit your php5 extensions requirements)

In order to make use of the freshly installed php under fastcgi we will need to enable fastcgi/php support per virtualhost basis.
So assuming you have the domain.com this is what the virtualhost configuration should look like:
(You may have other config lines and stuff , i am just giving you an example)

<VirtualHost www.domain.com:80>
ServerName www.domain.com
ServerAlias domain.net
ServerAdmin admin@domain.com
DocumentRoot /var/www/dn

<Directory /var/www/domain>
AddHandler fcgid-script .php
FCGIWrapper /usr/lib/cgi-bin/php5 .php
Options ExecCGI Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
allow from all
</Directory>

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
<Directory "/usr/lib/cgi-bin">
AllowOverride None
Options ExecCGI -MultiViews +SymLinksIfOwnerMatch
Order allow,deny
Allow from all
</Directory>

ErrorLog /var/log/apache2/domain-error.log
CustomLog /var/log/apache2/domain-access.log combined
LogLevel warn
ServerSignature On
</VirtualHost>

All the trick is done by these lines:

AddHandler fcgid-script .php
FCGIWrapper /usr/lib/cgi-bin/php5 .php
Options ExecCGI

Now you should just restart apache and test out your new domain by using

<?php phpinfo(); ?>

inside a newly created index.php file. (or you can name whatever you want)

I hope this does help you folks
Over and out

Andy

Chapter 1 – Basic configuration

First we should have (i assume you already have) installed the vsftpd daemon and the libpam-mysql and mysql.

#apt-get install vsftpd libpam-mysql mysql-server

Even if the purpose of the howto is to work with mysql stored username we will need to create a local user. Create it and all aditional directories:

#mkdir /home/ftp
#useradd ftpguest -d /home/ftp
#chown ftpguest.nogroup /home/ftp

Next create the mysql ftp virtual user to operate on mysql:

#mysqladmin -u root -p create ftpvuser

Connect to the mysql server to create the database and to create the tables:

#mysql -u root -p
mysql> create database ftpvuser;
Query OK, 1 row affected (0.00 sec)
mysql> use ftpvuser;
Database changed
mysql> CREATE TABLE users (username varchar (20) NOT NULL,
-> password varchar(40) NOT NULL,
-> PRIMARY KEY (username)) TYPE=MyISAM;
Query OK, 0 rows affected, 1 warning (0.00 sec)

then grant permission to an user to this database:

mysql> grant select on ftpvuser.users to ftpguest@localhost identified by ‘YourPassword’;
Query OK, 0 rows affected (0.04 sec)

This next step is necessary only if you are going to setup Chapter 2 configuration for different users with different permissions.

mysql> insert into users (username,password) values (‘normal’,'555555′);
Query OK, 1 row affected (0.00 sec)
mysql> insert into users (username,password) values (‘admin’,'666666′);
Query OK, 1 row affected (0.00 sec)
mysql> insert into users (username,password) values (‘webmaster’,'777777′);
Query OK, 1 row affected (0.00 sec)
mysql>quit;

Next edit if it exists or create the vsftpd pam config under /etc/pam.d/vsftpd:

#nano -w /etc/pam.d/vsftpd

And add these lines:

auth required pam_mysql.so user=ftpguest passwd=YourPassword host=localhost db=ftpvuser table=users usercolumn=username passwdcolumn=password crypt=0
account required pam_mysql.so user=ftpguest passwd=YourPassword host=localhost db=ftpvuser table=users usercolumn=username passwdcolumn=password crypt=0

Now open up your /etc/vsftpd.conf. Edit it as you may see fit and setup all options you like then restart your vsftpd server:

#/etc/init.d/vsftpd stop
#/etc/init.d/vsftpd start

For the record some vsftpd.conf options that you will need to set are:

# comment this line to disable anonymous logins
#anonymous_enable=YES
# enable local access
local_enable=YES
# enable guest access
guest_enable=YES
guest_username=ftpguest
# chroot local users
chroot_local_user=YES

Now test your ftp server quickly. If you cannot login and you get the errror 500 OOPS : cap_set_proc that its because of the SELinux. To fix this problem you will need to load the capability module into your running kernel:

#modprobe capability

To load this module automatically at each server restart add the capability module to your /etc/modules.

If you would like to restrict access to the ftp server and allow it only from certain IP addresses you will need to make use of the tcp_wrappers and enable it in your /etc/vsftpd.conf:

# TCP Wrappers
tcp_wrappers=YES

Deny all incoming connections by default in /etc/hosts.deny by adding:

vsftpd: ALL

Specify the allowed connection in /etc/hosts.allow by adding:

vsftpd: 192.168.0.,210.83.200.200 : setenv VSFTPD_LOAD_CONF /etc/vsftpd/vsftpd.anonymous
vsftpd: ALL : setenv VSFTPD_LOAD_CONF /etc/vsftpd/vsftpd.virtual

Next create the necessary files:

#mkdir /etc/vsftpd/
#nano -w /etc/vsftpd/vsftpd.anonymous

and add to it:

anonymous_enable=YES

then

#nano -w /etc/vsftpd/vsftpd.virtual

and add to it:

anonymous_enable=NO

Note you should add the ftp users into your mysql database using phpmyadmin or by building your own web app to do that. I dont cover this aspect here.

Chapter 2 – Different users with different permissions (optional)

This is a standalone chapter apart form the original configuration. It shows how to create different users with different permissions using vsftpd configuration files. We have performed the mysql users config for this chapter in the previous step adding in the `users` table the users “normal”, “admin” and “webmaster”.

#nano -w /etc/vsftpd.conf

and add to it:

user_config_dir=/etc/vsftpd/vsftpd_user_conf

Now we should allow ordinary users to download/upload. For this we should do the following:

#mkdir /etc/vsftpd/vsftpd_user_conf
#nano /etc/vsftpd/vsftpd_user_conf/normal

with the following content

anon_world_readable_only=NO
write_enable=YES
anon_upload_enable=YES
anon_mkdir_write_enable=YES

Also we need to allow admins to download/upload/delete and so on:

#cp /etc/vsftpd/vsftpd_user_conf/normal /etc/vsftpd/vsftpd_user_conf/admin
#nano -w /etc/vsftpd/vsftpd_user_conf/admin

and make it look like:

# Allow rename and delete the file
anon_other_write_enable=YES
# Users have to be a local user with the same permissions
virtual_use_local_privs=YES
# allows documents attributes modifications
chmod_enable=YES

And the webmaster configuration file:

#cp /etc/vsftpd/vsftpd_user_conf/admin /etc/vsftpd/vsftpd_user_conf/webmaster

Edit the webmaster configuration files to look like:

#FTP home directory at the website’s home directory
local_root=/var/www
# Because the uploaded files are owned by ftpguest
# other users are not allowed to access these files
# and especially the apache user www-data. To fix this
# we specify the local umask to 033
local_umask=033

With all these being said i hope this helps you.
I have been looking long time ago for this kind of setup. I wrote this tutorial like 2 years ago and it used to be on my website before i had to shut it down. Then i lost my db backups and all my tutorials got lost. But i am re-writting them one by one and hopefully even more.

Thank you

Once you are sure all the above are available on your system you can proceed installing squid. I suggest installing squid from source tarball and compile it manually in order to enable the wccp features of it. So after you’ve got the latest squid source you compile it like this:

gw1-livent:~# wget http://www.squid-cache.org/Versions/v2/2.7/squid-2.7.STABLE3.tar.gz
–18:35:11– http://www.squid-cache.org/Versions/v2/2.7/squid-2.7.STABLE3.tar.gz
=> `squid-2.7.STABLE3.tar.gz’
Resolving www.squid-cache.org… 12.160.37.9
Connecting to www.squid-cache.org|12.160.37.9|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 1,782,040 (1.7M) [application/x-gzip]

100%[=========================================================>] 1,782,040 106.67K/s ETA 00:00

18:35:30 (95.71 KB/s) – `squid-2.7.STABLE3.tar.gz’ saved [1782040/1782040]

gw1-livent:~#

unpack the source code and proceed with configure

gw1-livent:~# tar zxf squid-2.7.STABLE3.tar.gz
gw1-livent:~# cd squid-2.7.STABLE3
gw1-livent:~/squid-2.7.STABLE3# ./configure –enable-linux-netfilter –enable-wccp && make && make install

After you have installed squid tweak it to fit your needs and make sure transprent proxying is turned on in the config file:

httpd_accel_host virtual
httpd_accel_port 80
httpd_accel_with_proxy on
httpd_accel_uses_host_header on

After you are done with the config file and you think all your config is ok initialize the squid cache by typing:

gw1-livent:~# squid -z

Now that squid is running we would like to redirect all the traffic to port 80 to the squid port 3128. This being said we can type:

gw1-livent:~# iptables -t nat -A PREROUTING -i eth0 -p tcp –dport 80 -j REDIRECT –to-port 3128

With traffic redirected to squid we need to bring up the GRE tunnel between the cisco router and and the linux box running squid:

gw1-livent:~# iptunnel add gre1 mode gre remote IP-ADDRESS-OF-ROUTER local IP-ADDRESS-OF-SQUID-CACHE dev eth0

and then setup a GRE loopback adapter that acts like the local endpoint for the tunnel

gw1-livent:~# ifconfig gre1 127.0.0.2 up
gw1-livent:~# echo 0 > /proc/sys/net/ipv4/conf/gre1/rp_filter

Now let’s proceed to the router configuration since the linux should be done. Login onto your cisco router and set it up to catch all outgoing web requests:

Cisco> enable
Cisco# config t
Cisco(config)# ip wccp version 1
Cisco(config)# ip wccp web-cache
Cisco(config)# int your-outgoing-interface
Cisco(config-if)# ip wccp web-cache redirect out
Cisco(config-if)# end
Cisco# write mem

Optionally you may want to define an access list to control what IP’s get cached content and what IP’s are allowed to get out directly on the internet.

Cisco> enable
Cisco# config t
Cisco(config)# ip wccp version 1
Cisco(config)# ip wccp web-cache redirect-list 150
Cisco(config)# access-list 150 permit tcp 192.168.1.0 0.0.0.255 any
Cisco(config)# access-list 150 deny tcp any any
Cisco(config)# int your-outgoing-interface
Cisco(config-if)# ip wccp web-cache redirect out
Cisco(config-if)# end
Cisco# write mem

With all these being said i recommend you reading even more to find out ways of getting out the most of the squid web-cache server either by using it’s builtin features or by using third-party addons to enhance it.

Over and out

Andy

I assume you’ve already logged in on your server. Allright. Let’s go to /usr/src.

gw1-livent:~# cd /usr/src/
gw1-livent:/usr/src#

We get the bind9 source.

gw1-livent:/usr/src# apt-get source bind9
Reading package lists… Done
Building dependency tree… Done
Need to get 4347kB of source archives.
Get:1 http://ftp.debian.org etch/main bind9 1:9.3.4-2etch3 (dsc) [897B]
Get:2 http://ftp.debian.org etch/main bind9 1:9.3.4-2etch3 (tar) [4044kB]
Get:3 http://ftp.debian.org etch/main bind9 1:9.3.4-2etch3 (diff) [302kB]
Fetched 4347kB in 1s (2971kB/s)
dpkg-source: extracting bind9 in bind9-9.3.4
dpkg-source: unpacking bind9_9.3.4.orig.tar.gz
dpkg-source: applying ./bind9_9.3.4-2etch3.diff.gz
gw1-livent:/usr/src#

We download the mysql-bind.tar.gz package from sourceforge.net (you may as well pick other mirror as i used Switch)

gw1-livent:/usr/src# wget http://switch.dl.sourceforge.net/sourceforge/mysql-bind/mysql-bind.tar.gz
–18:56:17– http://switch.dl.sourceforge.net/sourceforge/mysql-bind/mysql-bind.tar.gz
=> `mysql-bind.tar.gz’
Resolving switch.dl.sourceforge.net… 130.59.138.20, 2001:620:0:1b::20
Connecting to switch.dl.sourceforge.net|130.59.138.20|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 14,019 (14K) [application/x-tar]

100%[==============================================>] 14,019 –.–K/s

18:56:18 (93.41 KB/s) – `mysql-bind.tar.gz’ saved [14019/14019]

gw1-livent:/usr/src#

We unpack it and go into the newly created directory.

gw1-livent:/usr/src# tar zxvf mysql-bind.tar.gz
mysql-bind/
mysql-bind/COPYING
mysql-bind/mysqldb.h
mysql-bind/ChangeLog
mysql-bind/.cvsignore
mysql-bind/mysqldb.c~
mysql-bind/ChangeLog~
mysql-bind/CVS/
mysql-bind/CVS/Entries
mysql-bind/CVS/Root
mysql-bind/CVS/Repository
mysql-bind/mysqldb.c
mysql-bind/README
mysql-bind/README~
mysql-bind/zonetodb.c
gw1-livent:/usr/src# cd mysql-bind
gw1-livent:/usr/src/mysql-bind#

Now we will need to copy the necessary files into the bind9 source directory.

gw1-livent:/usr/src/mysql-bind# cp mysqldb.c ../bind9-9.3.4/bin/named/
gw1-livent:/usr/src/mysql-bind# cp mysqldb.c ../bind9-9.3.4/bin/named/include/
gw1-livent:/usr/src/mysql-bind# cp mysqldb.h ../bind9-9.3.4/bin/named/
gw1-livent:/usr/src/mysql-bind# cp mysqldb.h ../bind9-9.3.4/bin/named/include/

Now we will need to edit some files on the bind9 source before actually compiling it. But before we will need to install some other pre-requisites for this installation. As Debian default install doesnt have some packages that we need we will install them now.

gw1-livent:/usr/src/mysql-bind# apt-get install fakeroot debhelper libmysqlclient15-dev

We will edit the Makefile.in file in /usr/src/bind9-9.3.4/bin/named/ and add some proper values to DBDRIVER_OBJS, DBDRIVER_SRCS, DBDRIVER_INCLUDES and DBDRIVER_LIBS parameters. Now open /usr/src/bind9-9.3.4/bin/named/Makefile.in with your favourite editor and search for:

#
# Add database drivers here.
#
DBDRIVER_OBJS =
DBDRIVER_SRCS =
DBDRIVER_INCLUDES =
DBDRIVER_LIBS =

.. which should at this step look like

#
# Add database drivers here.
#
DBDRIVER_OBJS = mysqldb.@O@
DBDRIVER_SRCS = mysqldb.c
DBDRIVER_INCLUDES =
DBDRIVER_LIBS =

For the next two values we will need to find out mysql configuration values that we will insert.
First let’s find for DBDRIVER_INCLUDES:

gw1-livent:/usr/src/bind9-9.3.4/bin/named# mysql_config –cflags
-I/usr/include/mysql -DBIG_JOINS=1
gw1-livent:/usr/src/bind9-9.3.4/bin/named#

Second DBDRIVER_LIBS …

gw1-livent:/usr/src/bind9-9.3.4/bin/named# mysql_config –libs
-L/usr/lib/mysql -lmysqlclient
gw1-livent:/usr/src/bind9-9.3.4/bin/named#

Now we add these values to the same part in Makefile.in so it looks like:

#
# Add database drivers here.
#
DBDRIVER_OBJS = mysqldb.@O@
DBDRIVER_SRCS = mysqldb.c
DBDRIVER_INCLUDES = -I/usr/include/mysql -DBIG_JOINS=1
DBDRIVER_LIBS = -L/usr/lib/mysql -lmysqlclient

Ok, we are done with this file. We are gonna edit now /usr/src/bind9-9.3.4/bin/named/main.c. Open it in your favorite editor and look for:

#include <dst /result.h>

/*
* Defining NS_MAIN provides storage declarations (rather than extern)
* for variables in named/globals.h.
*/

After #include on a new line add #include “include/mysqldb.h” so it looks like:

#include <dst /result.h>
#include "include/mysqldb.h"

/*
* Defining NS_MAIN provides storage declarations (rather than extern)
* for variables in named/globals.h.
*/

In the same file main.c search for:

/*
* Add calls to register sdb drivers here.
*/
/* xxdb_init(); */

ns_server_create(ns_g_mctx, &ns_g_server);
}

and change it so it looks like

/*
* Add calls to register sdb drivers here.
*/
/* xxdb_init(); */
mysqldb_init();
ns_server_create(ns_g_mctx, &ns_g_server);
}

then search for:

/*
* Add calls to unregister sdb drivers here.
*/
/* xxdb_clear(); */

isc_log_write(ns_g_lctx, NS_LOGCATEGORY_GENERAL, NS_LOGMODULE_MAIN,

and make sure it looks like:

/*
* Add calls to unregister sdb drivers here.
*/
/* xxdb_clear(); */
mysqldb_clear();
isc_log_write(ns_g_lctx, NS_LOGCATEGORY_GENERAL, NS_LOGMODULE_MAIN,

Save the file main.c and exit now. We are gonna make one more change in the file mysqldb.c that came in the mysql-bind package since it’s broken.
Open the file /usr/src/bind9-9.3.4/bin/named/mysqldb.c in your favorite text editor and look for the last include line that should look like:

#include <named /mysqldb.h>

Change the line so it looks:

#include “include/mysqldb.h”

As we are done editing the files we can now proceed with the build of bind9-mysql debian packages. Change the directory to /usr/src/bind9-9.3.4

gw1-livent:/usr/src/bind9-9.3.4/bin/named# cd ../../
gw1-livent:/usr/src/bind9-9.3.4#

Build it.

gw1-livent:/usr/src/bind9-9.3.4# dpkg-buildpackage -rfakeroot -b

If you get a message like:

dpkg-buildpackage: source package is bind9
dpkg-buildpackage: source version is 1:9.3.4-2etch3
dpkg-buildpackage: source changed by LaMont Jones
dpkg-buildpackage: host architecture i386
dpkg-buildpackage: source version without epoch 9.3.4-2etch3
dpkg-checkbuilddeps: Unmet build dependencies: bison texlive-latex-base xsltproc
dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting.
dpkg-buildpackage: (Use -d flag to override.)

then you will need to install the extra required packages by issuing:

gw1-livent:/usr/src/bind9-9.3.4# apt-get install bison texlive-latex-base xsltproc

The apt-get install process will ask your confirmation regarding the installation of these packages and as soon as you agree it will go downloading and installing them. Assuming you didnt need to do this step or that you didnt even encountered we continue.
After the dpkg-buildpackage is done and successfull you should see at the end among the last few lines:

dpkg-deb: building package `bind9′ in `../bind9_9.3.4-2etch3_i386.deb’.
dpkg-deb: building package `bind9-host’ in `../bind9-host_9.3.4-2etch3_i386.deb’.
dpkg-deb: building package `libbind-dev’ in `../libbind-dev_9.3.4-2etch3_i386.deb’.
dpkg-deb: building package `libbind9-0′ in `../libbind9-0_9.3.4-2etch3_i386.deb’.
dpkg-deb: building package `libdns22′ in `../libdns22_9.3.4-2etch3_i386.deb’.
dpkg-deb: building package `libisc11′ in `../libisc11_9.3.4-2etch3_i386.deb’.
dpkg-deb: building package `liblwres9′ in `../liblwres9_9.3.4-2etch3_i386.deb’.
dpkg-deb: building package `libisccc0′ in `../libisccc0_9.3.4-2etch3_i386.deb’.
dpkg-deb: building package `libisccfg1′ in `../libisccfg1_9.3.4-2etch3_i386.deb’.
dpkg-deb: building package `dnsutils’ in `../dnsutils_9.3.4-2etch3_i386.deb’.
dpkg-deb: building package `lwresd’ in `../lwresd_9.3.4-2etch3_i386.deb’.

That means that all required bind9 debian packages were built and they are available one directory before the bind9 source. Therefore we go up one directory:

gw1-livent:/usr/src/bind9-9.3.4# cd ../
gw1-livent:/usr/src#

and install our fresh built bind9 with mysql backend with all the other bind9 related libraries and utilities:

gw1-livent:/usr/src# dpkg -i bind9_9.3.4-2etch3_i386.deb bind9-doc_9.3.4-2etch3_all.deb bind9-host_9.3.4-2etch3_i386.deb dnsutils_9.3.4-2etch3_i386.deb libbind9-0_9.3.4-2etch3_i386.deb libbind-dev_9.3.4-2etch3_i386.deb libdns22_9.3.4-2etch3_i386.deb libisc11_9.3.4-2etch3_i386.deb libisccc0_9.3.4-2etch3_i386.deb libisccfg1_9.3.4-2etch3_i386.deb liblwres9_9.3.4-2etch3_i386.deb lwresd_9.3.4-2etch3_i386.deb

This is about all about building bind9 with mysql on Debian Etch.

Now you will need a basic structure for your mysql domain database and an example of how to add a domain to your named.conf.

The entry in named.conf will look something like this:

zone “mydomain.com” {
type master;
notify no;
database “mysqldb dbname tablename hostname user password”;
};

You should create a database for the driver and add one table for each domain. The following SQL will create a table for one domain. Change mydomain to something that will represent the domain more clearly.

CREATE TABLE mydomain (
name varchar(255) default NULL,
ttl int(11) default NULL,
rdtype varchar(255) default NULL,
rdata varchar(255) default NULL
) TYPE=MyISAM;

The following is an SQL dump of an example table for a domain. The entries should be familiar to anyone who is familiar with BIND zone files. Change it to match your domain.

INSERT INTO mydomain VALUES (‘mydomain.com’, 259200, ‘SOA’, ‘mydomain.com. www.mydomain.com. 200309181 28800 7200 86400 28800′);
INSERT INTO mydomain VALUES (‘mydomain.com’, 259200, ‘NS’, ‘ns0.mydomain.com.’);
INSERT INTO mydomain VALUES (‘mydomain.com’, 259200, ‘NS’, ‘ns1.mydomain.com.’);
INSERT INTO mydomain VALUES (‘mydomain.com’, 259200, ‘MX’, ‘10 mail.mydomain.com.’);
INSERT INTO mydomain VALUES (‘w0.mydomain.com’, 259200, ‘A’, ‘192.168.1.1′);
INSERT INTO mydomain VALUES (‘w1.mydomain.com’, 259200, ‘A’, ‘192.168.1.2′);
INSERT INTO mydomain VALUES (‘mydomain.com’, 259200, ‘Cname’, ‘w0.mydomain.com.’);
INSERT INTO mydomain VALUES (‘mail.mydomain.com’, 259200, ‘Cname’, ‘w0.mydomain.com.’);
INSERT INTO mydomain VALUES (‘ns0.mydomain.com’, 259200, ‘Cname’, ‘w0.mydomain.com.’);
INSERT INTO mydomain VALUES (‘ns1.mydomain.com’, 259200, ‘Cname’, ‘w1.mydomain.com.’);
INSERT INTO mydomain VALUES (‘www.mydomain.com’, 259200, ‘Cname’, ‘w0.mydomain.com.’);
INSERT INTO mydomain VALUES (‘ftp.mydomain.com’, 259200, ‘Cname’, ‘w0.mydomain.com.’);

With all these being said i really hope this article helps many of you. It took some time to elaborate and make it step by step but it worths. I will also attach the packages built for this tutorial for those that will simply want to get them, install them and have it running.

Note: the downloads below are available only for registered members of Digitalnerds.

Thank you very much for your attention.

The Digitalnerd

The search for a new lead has been shrouded in secrecy, but sources say Fishburne is being heavily courted to play the new character, described as a doctor/scientist outsider to the CSI unit who has the same genetic profile as a serial killer but hasn’t previously acted on any homicidal impulses.

Fishburne, an Oscar nominee for “What’s Love Got to Do With It,” had been mentioned as one of the “CSI” producers’ top choices for the role, along with John Malkovich and Kurt Russell.

Following the incident, which Jermaine hosted to kick-off his annual So So Def SummerFest, the music producer said:

I’m sad this incident happened because it interrupted a beautiful and loving party. But I’m happy none of my people or friends got hurt. And the party continues.

While no celebrity guests were injured in the shooting, the gunman shot one of the club’s security guards in the arm.

The guard was taken to hospital for treatment before being released. Police are still interviewing witnesses in a bid to determine the identity of the shooter.

Despite the fact The Mummy 3: Tomb of the Dragon Emperor has only a 6.5 out of 10 rating on IMDb, i personally like this movie.
But in order to be objective i must say that except the actors and probably the director. the WRITTERS SUCKED BADLY. How could you have at your disposal such a rich history, culture and art as the China’s one and use almost nothing of it.
Brendan Fraser & Jet Li. Now come on, what could you ask more. I really like the Mummy series for its epic action, sense of humor and great special effects. I was very excited when I started seeing teasers for this sequel to be shown in July, mostly because it was quite unexpected.
For the new stuff, the setting shift to China as the titular “Mummy” now refers to an ancient Chinese emperor who desired immortality, played by Jet Li (who really personified his anti-hero role with relish here). The emperor sought the help of a “witch” (played with much bravado by Michelle Yeoh), with whom he gets attracted to. However, the witch fell in love with his main general (played by Russell Wong, whom you’d wonder why he isn’t getting more breaks in Hollywood). From hence starts the conflict and the resultant curse on which the movie stands.

The requisite martial arts you would expect in a movie set in China are of course in full play. Very well choreographed, especially that thrilling sword fight between Jet Li and Michelle Yeoh. The exciting action sequences inside the booby-trapped lost tomb, the truck and chariot (!) chase in the streets of Shanghai and the final fight sequence with the “Mummy” are all executed very well as in the two previous installments.

But there are many other drawbacks and the most important is that i really miss Rachel Weisz. Maria Bello has absolutely no relation with the movie itself and i wonder how she ended up on the set.
Anyway i will let you watch this movie and see for yourself. Maybe you will love it even more. But not before to ask a last question…………………  Exactly what is wrong with Hollywood????.