Question : Why will one DNS alias name not resolve when others will - Bind

I am using BIND (Version 9)  for DNS services and I have a strange problem.

I have a development system with several aliases and only one is not resolving unless FQDN is used.  Thesea re all internal addresses only and all resolve to the same IP.
For example:

social.system               IN A 192.168.0.107
admin.system              IN A 192.168.0.107
sales.system                IN A 192.168.0.107
dash.system                IN A 192.168.0.107
dashboard.system       IN A 192.168.0.107
store.system                IN A 192.168.0.107

in this list . .. the only one that will not return a ping is dashboard.system
I can ping every other one and I can ping dashboard.system if I ping FQDN.  

dolphin.system.mycompany.com

I have restarted named and added ones since and still that is the only one that will not resolve  

nslookup from my vista box to the DNS server (with FQDN) will also return proper IP)

Any thoughts why?

Answer : Why will one DNS alias name not resolve when others will - Bind

> in this list . .. the only one that will not return a ping is dashboard.system

My next suggestion is that this name is too long for windows :-) I bet it will resolve dashboar.system (15 chars long) as it is a valid NetBIOS PC name length. dashboard.system is the only name >15 chars (16 chars long), all the others are shorter.