<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto">Hi Bob,<div dir="auto"><br></div><div dir="auto">I've been able to do this with 'forward' zones. The config would go in the resolver but the files would not.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">/John</div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:#000000"><div>-------- Original message --------</div><div>From: Bob McDonald <bmcdonaldjr@gmail.com></div><div><br></div></div>I'm thinking about redesigning an internal DNS environment. To begin<br dir="auto">with, all internal DNS zones would reside on non-recursive servers<br dir="auto">only. That said, all clients would connect to recursive resolvers.<br dir="auto"><br dir="auto">The question is this; do I use an internal root with pointers to the<br dir="auto">internal zones (as well as the outside DNS world) or do I include stub<br dir="auto">zones to point at the non-recursive internal servers?<br dir="auto"><br dir="auto">Access to the internal DNS zones would be controlled by location.<br dir="auto">(e.g. guest WiFi devices would NOT have access to internal DNS<br dir="auto">zones...)<br dir="auto"><br dir="auto">Recursive resolvers would allow implementation of features such as RPZ, etc.<br dir="auto"><br dir="auto">Regards,<br dir="auto"><br dir="auto">Bob<br dir="auto">-- <br dir="auto">Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list<br dir="auto"><br dir="auto">ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.<br dir="auto"><br dir="auto"><br dir="auto">bind-users mailing list<br dir="auto">bind-users@lists.isc.org<br dir="auto">https://lists.isc.org/mailman/listinfo/bind-users<br dir="auto"><br dir="auto"></body></html>