Why named forwards NS queries when is autoritative for upperdomain?

11 msg	bind-dlz
3 msg	bind-9.4.2, notify, slave and views; supported?
7 msg	testing bind-dlz
4 msg	external DNS
4 msg	Misfeature of 9.4.2 named-checkzone
3 msg	Strange _default view error
4 msg	one more nsupdate question..
2 msg	nsupdate cannot update, only add or delete
25 msg	max-cache-size doesn't work with 9.5.0b1
3 msg	Problem with Views and restricting recursive qu...
1 msg	notify - ixfr to interface alias problem ** Sol...
2 msg	Memory management. 'USE INTERNAL MALLOC' is now...
3 msg	notify - ixfr to interface alias problem
2 msg	Taub, Beau is out of the office.
2 msg	only for translate ...
6 msg	Bind /named stopped working - getting SERVFAIL
2 msg	Need a little help with recursion in Bind
65 msg	From RHEL to CentOS BIND 9

Why named forwards NS queries when is autoritat...
\ Adam Tkac (4 Dec 2007)
. \ Chris Buxton (4 Dec 2007)

1 msg	Bind 9.3.4P1 Wouldn't run in Sandbox in FreeBSD...

Subject:	Why named forwards NS queries when is autoritative for upperdomain?
Group:	Bind-users
From:	Adam Tkac
Date:	4 Dec 2007

Hi all,

recetly I've found interesting behavior. I have domain b.a. and
subdomain c.b.a. There's no delegation from b.a. to c.b.a. Server
which is autoritative for c.b.a. has server for b.a. as forwarder.
On server for c.b.a. I've set new subdomain d.c.b.a. with proper
delegation. But when I query "c.b.a." server for NS records of
d.c.b.a. subdomain I get NXDOMAIN from b.a. nameserver. Could anybody
here point me why this doesn't work? I don't use forward {first,only}
options.

Regards, Adam

--
Adam Tkac, Red Hat, Inc.