<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On Apr 20, 2011, at 2:19 AM, Adam Goodall wrote:</div><div><blockquote type="cite">However if a client queries server A for <a href="http://mail.testdomain.com/">mail.testdomain.com</a> (type any) the request is not answered. From the logs on server B i can see that server A is only forwarding on a request of type A. As an A record for <a href="http://mail.testdomain.com/">mail.testdomain.com</a> does not exist on server B it does not resolve.<br>
<br>If i then specifically query Server A for <a href="http://mail.testdomain.com/">mail.testdomain.com</a> of type CNAME, it resolves as expected. Subsequent requests against server A for <a href="http://mail.testdomain.com/">mail.testdomain.com</a> of type any then resolve, presumably because it is already in the cache.<br>
<br>Hopefully that makes sense! Has anyone had a similar issue and did you come up with a work around? Is this expected behaviour or a bug?<br></blockquote></div><br><div>This is an excellent example of why you should not forward to an auth-only server. Use a stub zone instead. You might need to give it an empty forwarders list, to override forwarding set in either the options or view statements.</div><div><br></div><div>For example:</div><div><br></div><div>zone "<a href="http://testdomain.com">testdomain.com</a>" {</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>type stub;</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>masters { 192.168.1.1; };</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>forwarders { };</div><div>};</div><div><br></div><div>Try it, you'll like it.</div><div><br></div><div>Chris Buxton</div><div>BlueCat Networks</div><div><br></div></body></html>