On Jan 24, 2011, at 5:59 AM, Cathy Almond wrote: >> I wonder, what are expected usages for this kinds of zones? >> Maybe blacklists, if we have local mirrors and traffic so high that we'd get >> blocked imediately? > > It's subtle. > > One use case is for testing new servers that aren't yet part of the main > Internet name space. You can force queries for that zone to go to your > test servers (maybe they're running new software, maybe they're testing > DNSSEC, maybe... ) instead of the servers that would be located the via > delegation from the parent zone. In this instance the test servers > might well need to respond with the 'real' nameserver information (for > returning to clients) - but you don't want that to override the fact > that you still want to send future queries to the servers you have on test.
Another use is to separate recursion from internal authoritative name servers. You could put this on the recursing name servers, telling them explicitly which auth servers to hit rather than relying on a traditional stub zone. This might be useful if the zone is hosted on some nearby servers and also some remote servers, to avoid having the RTT algorithm cause the recursing server to query the remote servers. Chris Buxton BlueCat Networks _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
