subdomain forwarders problem

Dave dmcpike at
Wed Nov 24 22:41:05 UTC 1999

> global forwarder's address. Are you seeing something different from that? Is
> there something perhaps wrong with your forwarder?Have you tried just bouncing
> regular recursive queries of the same names off that forwarder using, say,
> nslookup or dig?

dig produces the same results.  Here's what I see from the debug log:

req: nlookup( id 35552 type=1 class=1
req: found '' as '' (cname=0)
findns: SOA found
req: leaving (, rcode 0)
free_nsp: rcnt 1
doaddinfo() addcount = 1
do additional "name.dom" (from "name.dom")
found it
ns_req: answer -> [].1041 fd=20 id=35552 size=102 rc=0

corp is just another subdomain in name.dom.   The forwarding functions
take place as you outlined as soon as I comment the "name.dom" zone statements below.

and this is all I have in /etc/named.conf:

options {
	directory "/var/named";
	forward only;
	forwarders {;;

zone "." in {
	type hint;
	file "named.root";
zone "0.0.127.IN-ADDR.ARPA" in {
	type master;
	file "named.local";

zone "name.dom" in {
	type master;
	file "primary/name.dom";

Thanks a lot for any input!


More information about the bind-users mailing list