Setting up a dns server on CentOs 5.8

I'm having some problems with setting up my dns server on my vps (CentOs 5.8 32 bit)

I have configured a dns zone with the ISPConfig 3 wizard.
My name servers are registered at my domain registrar (at Yahoo)

I configured my domain to use my name servers:

ns1.mydomain.com
ns2.mydomain.com

Still, when I go to my domain, it says page not found.

The real error is "can't find domainname.com"

named.conf (in /var/named/chroot/etc)

//
// Sample named.conf BIND DNS server 'named' configuration file
// for the Red Hat BIND distribution.
//
// See the BIND Administrator's Reference Manual (ARM) for details, in:
//   file:///usr/share/doc/bind-*/arm/Bv9ARM.html
// Also see the BIND Configuration GUI : /usr/bin/system-config-bind and
// its manual.
//
options
{
    // Those options should be used carefully because they disable port
    // randomization
    // query-source    port 53;
    // query-source-v6 port 53;

    // Put files that named is allowed to write in the data/ directory:
    directory "/var/named"; // the default
    dump-file               "data/cache_dump.db";
    statistics-file         "data/named_stats.txt";
    memstatistics-file      "data/named_mem_stats.txt";

};
logging
{
/*      If you want to enable debugging, eg. using the 'rndc trace' command,
 *      named will try to write the 'named.run' file in the $directory (/var/named).
 *      By default, SELinux policy does not allow named to modify the /var/named  directory,
 *      so put the default debug log file in data/ :
 */
     channel default_debug {
         file "data/named.run";
         severity dynamic;
     };
};
//
// All BIND 9 zones are in a "view", which allow different zones to be served
// to different types of client addresses, and for options to be set for groups
// of zones.
//
// By default, if named.conf contains no "view" clauses, all zones are in the
// "default" view, which matches all clients.
//
// If named.conf contains any "view" clause, then all zones MUST be in a view;
// so it is recommended to start off using views to avoid having to restructure
// your configuration files in the future.
//