Linux Bind delegation problem

Hi,

I'm trying to setup a delegation zone in my internal network, i've read
a lot, googled a lot but still it doesn't work
My main DNS server (192.168.1.5) has:
file named.conf
.......
zone "zeca.maneca" {
type master;
notify no;
file "zeca.maneca.db";
allow-transfer { 127.0.0.1; };
};
..........
file zeca.maneca.db
$ORIGIN zeca.maneca.
$TTL 900 ; 15 minutes
@ IN SOA zeca.maneca. root (
2004041700 ; serial
21600 ; refresh (6 hours)
1800 ; retry (30 minutes)
604800 ; expire (1 week)
900 ; minimum (15 minutes)
)
IN A 192.168.1.5
IN NS jimi.liber4e.zapto.org. (other zone i have
configured)
hosting-test NS nameserver.hosting-test.zeca.maneca.
nameserver.hosting-test IN A 192.168.1.100

My delegated server (192.168.1.100) has
file named.conf
.........
zone "hosting-test.zeca.maneca" IN {
type master;
file "hosting-test.zeca.maneca.zone";
};
............

file hosting-test.zeca.maneca.zone
$ORIGIN hosting-test.zeca.maneca.
$TTL 900 ; 15 minutes
@ IN SOA hosting-test.zeca.maneca. root (
2004041700 ; serial
21600 ; refresh (6 hours)
1800 ; retry (30 minutes)
604800 ; expire (1 week)
900 ; minimum (15 minutes)
)
IN A 192.168.1.100
IN NS nameserver.hosting-test.zeca.maneca.
nameserver IN A 192.168.1.100

#####################################

When I do:
dig hosting-test.zeca.maneca
; <<>> DiG 9.2.3 <<>> hosting-test.zeca.maneca
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30745
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;hosting-test.zeca.maneca. IN A

;; Query time: 132 msec
;; SERVER: 192.168.1.5#53(192.168.1.5)
;; WHEN: Tue Sep 14 17:48:01 2004
;; MSG SIZE rcvd: 42

###################################

and when I do:
dig hosting-test.zeca.maneca @192.168.1.100
; <<>> DiG 9.2.3 <<>> hosting-test.zeca.maneca @192.168.1.100
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25929
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;hosting-test.zeca.maneca. IN A

;; ANSWER SECTION:
hosting-test.zeca.maneca. 900 IN A 192.168.1.100

;; AUTHORITY SECTION:
hosting-test.zeca.maneca. 900 IN NS
nameserver.hosting-test.zeca.maneca.

;; ADDITIONAL SECTION:
nameserver.hosting-test.zeca.maneca. 900 IN A 192.168.1.100

;; Query time: 12 msec
;; SERVER: 192.168.1.100#53(192.168.1.100)
;; WHEN: Tue Sep 14 17:48:09 2004
;; MSG SIZE rcvd: 99

What I'm missing here? any hints are very welcome

Best regards

Jose' Nuno Neto

Try reloading the configuration on 192.168.1.5.

Yep I've quite a few reload or restart
and check /var/log/messages and everything loads fine
but in your opinion there's no configuration error?

Well you've got the right idea, as for whether there's a typo in there I can't tell ya cause I'm only human and might've missed it too. So let's see what BIND has to say. Shut down the DNS server on 192.168.1.5 (cause that's where the problem is at) and execute the following command on it. Paste for me the results:

named -u named -g

It's chrooted...
named -u named -g -t /var/named/chroot
Sep 14 14:18:00.225 starting BIND 9.2.2-P3 -u named -g -t /var/named/chroot
Sep 14 14:18:00.228 using 1 CPU
Sep 14 14:18:00.266 loading configuration from '/etc/named.conf'
Sep 14 14:18:00.408 no IPv6 interfaces found
Sep 14 14:18:00.409 listening on IPv4 interface lo, 127.0.0.1#53
Sep 14 14:18:00.413 binding TCP socket: address in use
Sep 14 14:18:00.414 listening on IPv4 interface eth0, 213.22.208.30#53
Sep 14 14:18:00.415 binding TCP socket: address in use
Sep 14 14:18:00.415 listening on IPv4 interface eth1, 192.168.1.5#53
Sep 14 14:18:00.416 binding TCP socket: address in use
Sep 14 14:18:00.454 /etc/named.conf:19: couldn't add command channel 127.0.0.1#953: address in use
Sep 14 14:18:00.455 ignoring config file logging statement due to -g option
Sep 14 14:18:00.470 zone 0.0.127.in-addr.arpa/IN: loaded serial 1
Sep 14 14:18:00.482 zone 1.168.192.in-addr.arpa/IN: loaded serial 2004041700
Sep 14 14:18:00.495 zone zeca.maneca/IN: loaded serial 2004041700
Sep 14 14:18:00.509 zone liber4e.zapto.org/IN: loaded serial 199802151
Sep 14 14:18:00.511 running

What's the meaning of this?
/etc/named.conf:19: couldn't add command channel 127.0.0.1#953: address in use

named.conf:19: has this
controls {
inet 127.0.0.1 allow { localhost; } ;
};

Did a
killall -KILL named
and restarted now:

named -u named -g -t /var/named/chroot
Sep 14 14:32:42.643 starting BIND 9.2.2-P3 -u named -g -t /var/named/chroot
Sep 14 14:32:42.646 using 1 CPU
Sep 14 14:32:42.684 loading configuration from '/etc/named.conf'
Sep 14 14:32:42.829 no IPv6 interfaces found
Sep 14 14:32:42.830 listening on IPv4 interface lo, 127.0.0.1#53
Sep 14 14:32:42.835 listening on IPv4 interface eth0, 213.22.208.30#53
Sep 14 14:32:42.837 listening on IPv4 interface eth1, 192.168.1.5#53
Sep 14 14:32:42.876 command channel listening on 127.0.0.1#953
Sep 14 14:32:42.877 ignoring config file logging statement due to -g option
Sep 14 14:32:42.892 zone 0.0.127.in-addr.arpa/IN: loaded serial 1
Sep 14 14:32:42.905 zone 1.168.192.in-addr.arpa/IN: loaded serial 2004041700
Sep 14 14:32:42.917 zone zeca.maneca/IN: loaded serial 2004041700
Sep 14 14:32:42.932 zone liber4e.zapto.org/IN: loaded serial 199802151
Sep 14 14:32:42.934 running

but still no response from delegated zone

Please attach your named.conf. I'm going to make sure you edited the right file.

Here goes
I added the logging option to check whats wrong but it shoes nothing

cat /var/named/ch*/etc/named.conf
options {
directory "/var/named/";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
query-source address * port 53;

// Forward any unresolved requests to our ISP's name server

forwarders {212.113.161.226; 212.113.161.227;};
};


# Setup logging
logging {
# Each channel defines a file path and what to log
# Each category is a type of event you wish to log
# You define channels and associate them with a category to log events
#
channel query_logging {
# If you enable query logging, make sure to change the path to a valid directory
#
# version: number of backups created if size exceeded
# size : maximum size of log file
#
file "/var/log/named/query.log" versions 3 size 100M;

# Time stamp entries
#
print-time yes;
};
category queries {
# Uncomment the below line to enable query logging
query_logging;
};
category lame-servers { null; };
};







zone "." {
type hint;
file "named.ca";
};

zone "0.0.127.in-addr.arpa" {
type master;
file "localhost.zone";
};

zone "1.168.192.in-addr.arpa" {
type master;
file "192.168.1.zone";
};



zone "liber4e.zapto.org" {
type master;
notify no;
file "liber4e.zapto.org.db";
allow-transfer { 127.0.0.1; };
};

zone "zeca.maneca" {
type master;
notify no;
file "zeca.maneca.db";
allow-transfer { 127.0.0.1; };

};

include "/etc/rndc.key";

Ok good, now execute this cat command:

cat /var/named/chroot/var/named/zeca.maneca.db

cat /var/named/chroot/var/named/zeca.maneca.db
$ORIGIN zeca.maneca.
$TTL 900 ; 15 minutes
@ IN SOA zeca.maneca. root (
2004041700 ; serial
21600 ; refresh (6 hours)
1800 ; retry (30 minutes)
604800 ; expire (1 week)
900 ; minimum (15 minutes)
)
IN A 192.168.1.5
IN NS jimi.liber4e.zapto.org.
hosting-test NS nameserver.hosting-test.zeca.maneca.
nameserver.hosting-test IN A 192.168.1.100

I was hoping you misrepresented the circumstances, but apparently not. Now let me see the response to this command:

dig @192.168.1.5 zeca.maneca axfr