I disagree with your statement about recursion. What stops an authoritative server from doing recursion if you do not have the recursion statement? I guess the bind default is recursion yes.
-----Original Message----- From: Chris Buxton [mailto:cli...@buxtonfamily.us] Sent: Thursday, March 28, 2013 11:49 AM To: Manson, John Cc: bind-users@lists.isc.org Subject: Re: Recursion issue On Mar 28, 2013, at 8:27 AM, Manson, John wrote: > From the internet: > Answer records > > name class type data time to live > test.gopleader.gov IN CNAME testwww.house.gov > > Testwww from the internet: > Answer records > > name class type data time to live > testwww.house.gov IN A 12.13.14.15 900s (00:15:00) > > So the first lookup does not fully resolve due to recursion. > Does this help? Yes it does. It just doesn't all get answered from the one zone. Both of your public servers, chyron and mercury, contain both zones. A non-recursive query to either of them gets both records in an authoritative answer. $ dig test.gopleader.gov +norec @mercury.house.gov ; <<>> DiG 9.7.6-P1 <<>> test.gopleader.gov +norec @mercury.house.gov ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26756 ;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;test.gopleader.gov. IN A ;; ANSWER SECTION: test.gopleader.gov. 300 IN CNAME testwww.house.gov. testwww.house.gov. 900 IN A 12.13.14.15 ;; Query time: 100 msec ;; SERVER: 143.231.1.67#53(143.231.1.67) ;; WHEN: Thu Mar 28 08:45:23 2013 ;; MSG SIZE rcvd: 80 There is no need to configure recursion on your external authoritative name servers. Other name servers will not query them recursively anyway. I continue to fail to see the problem that you're trying to solve. Chris Buxton BlueCat Networks _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
