>1. The root server entries would sometimes duplicate and then quit responding >2. After the TTL expired for some sites would expire, we could not get them > to renew without deleting the sites folder from the cache. This > happened > multiple times and was a real headache.
This is really quirky stuff, hard to understand and debug, and it's the kind of stuff that causes many people, but obviously not all, to move to some other DNS server. I helped a guy last night move to bind since was apparently being attacked with bad DNS packets that screwed up MS DNS. More insufficiently "defensive" programming from MS. BIND 8 is working fine on the same machine, and apparently under the same attack. Other situations where I hear there are MS DNS pb's are in heavy zone transfers to several slaves, large numbers of zones (100's or 1000's). ie, like a lot of MS stuff, it really isn't industrial strength code that you want to put into infrastructure roles. And NT4 and W2K DNS are both have poisonable caches out of the box that requires a registry hack to fix. None of this has anything to do with which radio buttons you click to set it up (which itself, anyway, shouldn�t be able to screw up the software). Plus MS DNS logging, critical to any debugging and operational validation, is really lightweight. But if it works for you, fine. Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
