Network issues since upgrading to Yosemite - Unable to find local systems
This is very common problem in split-horizon DNS and heterogenous but Windows-dominated company networks. A lot of Windows sysadmins are used to the .local TLD as a valid private TLD name since at least a decade though it's not RFC-compliant anymore.  

When your local area network has been configured with a domain name ending in .local, then all LAN hostname resolutions queried by a Mac will be passed to mDNS first - bypassing unicast DNS!

So hostname resolutions for .local often fail in Mac OS X applications (Safari, Chrome etc and often ping).

In contrary dig and nslookup are unicast DNS utilities, so they will both bypass the system hostname resolution order (files->mDNS->DNS) and query unicast DNS directly.

Some workarounds exist (your mileage will vary):  


flush DNS cache frequently
add prod.local as search domain (to add local additionally is sometimes advised as well)




IMHO the only proper and RFC-compliant way to fix this is changing the local domain names to use a TLD other than .local in your Windows corporate network.