Search Again: Re: recursive lookups-followup From: Brad Michels Date: Friday, December 13, 2002 Time: 9:32:20 am As a follow up, there is also the ability to build in Query restrictions and Transfer restrictions. Is it adviseable to limit both of these to servers within your own network and, as in our case where our ISP is our secondary, our secondary DNS? Thanks! Brad Michels Network Administrator East Grand School District Granby, Colorado 970-887-3312 bmichels@cubs.egsd.k12.co.us quickdns-talk@lists.menandmice.com writes: >By default, with the setting at recursive query resolving, your >server handles recursion itself. When a query comes in from a client >machine, your server does all the work necessary to resolve that name. > >With forwarding turned on, your server will simply relay the client >request to another DNS server, and let that other server do all the >heavy lifting. This is desirable in situations when a DNS server is >not able to access the Internet or has a slow Internet connection. > >Normally, when forwarding, the DNS server has a fairly short timeout >period for the forwarder (the upstream DNS server) to respond. If >that forwarder (or those forwarders) doesn't/don't respond in that >time, it will go ahead and try to do the lookup itself. If the "work >as slave server" option is turned on, it will not do this and will >rely entirely on its forwarders. >____________________________________________________________________ >Chris Buxton Men & Mice >support@menandmice.com Making DNS Easy

Messages In This Thread: Re: recursive lookups-followup by Brad Michels on Dec 13, 2002 at 9:32:20 am Re: recursive lookups-followup by Men & Mice Support on Dec 13, 2002 at 11:53:38 am Re: recursive lookups-followup by billc_lists@greenbuilder.com on Sep 6, 2003 at 11:51:09 pm Re: recursive lookups-followup by Men & Mice Support on Sep 7, 2003 at 3:22:11 pm