BIND in chroot

Hi all,
I'm trying to start named in chroot environment manually but i'm getting the following error

bash-3.00# cat /etc/release
                     Solaris 10 6/06 s10s_u2wos_09a SPARC
           Copyright 2006 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                             Assembled 09 June 2006
 
bash-3.00# uname -a
SunOS mail 5.10 Generic_127111-05 sun4u sparc SUNW,Sun-Fire-880
bash-3.00# named -v
BIND 9.3.4-P1
bash-3.00# /usr/sbin/named -c /var/named/etc/named.conf  -t /var/named  -u named 
 -f -g
named: config filename (-c /var/named/etc/named.conf) contains chroot path (-t /var/named)
13-Sep-2012 12:07:12.328 starting BIND 9.3.4-P1 -c /var/named/etc/named.conf -t /var/named -u named -f -g
13-Sep-2012 12:07:12.328 found 4 CPUs, using 4 worker threads
13-Sep-2012 12:07:12.338 loading configuration from '/var/named/etc/named.conf'
13-Sep-2012 12:07:12.339 none:0: open: /var/named/etc/named.conf: file not found
13-Sep-2012 12:07:12.340 loading configuration: file not found
13-Sep-2012 12:07:12.340 exiting (due to fatal error)

What is the cause of the above error any idea will be a great assist

here is named.conf contents

bash-3.00# cat   /var/named/etc/named.conf

options {
  directory "/var/named";
  // version statement - inhibited for security
  // (avoids hacking any known weaknesses)      
  version "get lost";
  // optional - disables all transfers 
  // slaves allowed in zone clauses
  allow-transfer {"none";};
        // Closed DNS - permits only local IPs to issue recursive queries 
  // remove if an Open DNS required to support all users 
  // or add additional ranges 
  allow-recursion { 192.168.0.0/16; 172.16.0.0/16;};
};
//
// log to /var/log/named/example.log all events from 
// info UP in severity (no debug)
// defaults to use 3 files in rotation
// BIND 8.x logging MUST COME FIRST in this file
// BIND 9.x parses the whole file before using the log
// failure messages up to this point are in (syslog) 
// typically /var/log/messages
//
  logging{
  channel example_log{
   file "/var/named/var/log/example.log" versions 3 size 2m;
   severity info;
   print-severity yes;
   print-time yes;
   print-category yes;
 };
 category default{
  example_log;
 };
};
// required zone for recursive queries
zone "." {
  type hint;
  file "named.root";
};
// required local host domain
//zone "localhost" in{
//  type master;
//  file "master.localhost";
//  allow-update{none;};
//};
// localhost reverse map
//zone "0.0.127.in-addr.arpa" in{
//  type master;
//  file "localhost.rev";
//  allow-update{none;};
//};

Unless I missed something really important -

The standard uses /etc/named/named.conf. This has been the case for a long time. You cannot have the conf file inside your chroot jail because it compromises security.

Yours is inside the -t /var/named chroot.