Re: how to protect name servers against cache corruption

Correct me if I'm wrong, but this implies that nameservers whose sole purpose is to act as primary and secondary for customer domains can run with recursion disabled. I.e. all those nameservers whose identity is readily discernable from public databases such as the Internic, RIPE, etc., could run in this configuration as long as they are not also intended to do lookups for local machines on your local network.

That's the way we run ours (non-recursive) It keeps performance up too while keeping tabs on memory usage. In fact, we secondary commonly accessed domains directly from their authoritative nameservers and keep regular tabs on them to ensure our pointers are correct. -Deepak. AINet