> I reported this before. From two different sites I have the following
> problem: netbsd.org won't resolve, but NetBSD.ORG will. Once NetBSD.ORG
> is resolved, the local nameserver will cache it and correctly answer for
> netbsd.org in any caplitalization. Again, I see this on two completely
> seperate systems at two different companies a thousand mile appart
> who each use different service providers. So, the screwup must be at a
> fairly high level.

Sounds to me like *very* broken named implementations. What systems does this
error appear on? How is your resolver set up? local secondary named or
nameserver on another system? If nameserver on another system, what kind
of system is that other system?

Remember: different ISP can still use the same broken software. :)

Chris

-- 
Christian Kuhtz <kuhtz@isrl.cba.uni.edu>, http://www.cba.uni.edu/~kuhtz
IS Research Lab,College of Business Administration, University of Northern Iowa
Cedar Falls, IA, USA. Disclaimer: "If you think I speak for someone else than 
myself, then I've got some swamp land real estate to sell you."