> But the problem with health warnings is - where do you stop?
Two things. Firstly, of course it's not for me to say, as Kitz does the work around here, and I just enjoy the benefits. :-)
Secondly - Point taken about Google. But what I would say is that certain technical things, such as the return bogus page instead of a failure thing, are just examples of brokenness. That behavioural feature could be n-valued, (1) not broken - returns failures correctly vs (2) broken vs (3) broken by default, configurably 'fixable'.
Sticking to technical features avoids the mire of subjective judgements.
Another possible example would be uk-based server = TRUE/FALSE. Another one might be anycast=TRUE/FALSE.
For example Cisco's main name servers are usable by anyone AFAIK as presumably their own hardware needs them. I wouldn't recommend them for uk clients though as in my experience they're too far away and performance is therefore not ideal.
OpenDNS has 'rich' behaviour, not sure that's the right word. It adds complex behaviour on top of what a normal, straight DNS server will do. And some of this behaviour is very worthwhile, despite my criticism of them, and as it's configurable (now), this addresses some of my concerns. So anyway a "rich" flag might tell the reader that she/he needs to "read the manual".