The Core

Not seen one of these before;

Over the last 24 hours, Googlebot encountered 82 errors while attempting to retrieve DNS information for your site. The overall error rate for DNS queries for your site is 1.3%.

You can see more details about these errors in Webmaster Tools.
Recommended action
If the site error rate is 100%:
Use a WHOIS tool to verify that [domain] has a proper whois record and that nameservers are configured for the site. If not, contact your domain registrar to update your whois records.
Using a DNS lookup tool, verify that the nameserver's name can be resolved to an IP address. If not, either update your whois record to contain an IP address for your nameserver, or update the DNS records for nameserver.
Using a DNS lookup tool, verify that [domain] can be resolved to an IP address. If it can't, update the DNS record for [domain] on your nameserver.
If the site error rate is less than 100%:
The most likely explanation is that your nameserver is overloaded. Contact your hosting provider and discuss the configuration of your DNS server and the possibility of allocating more resources to your DNS service.
After you think you've fixed the problem, use Fetch as Google to verify that Googlebot can properly access your site.

Weird thing is, we can't find any issues or evidence that anyone has had issues. 

Those dns errors can be major screw ups.  We once had one over a small spammy loan network where G crawled the sites and decided they were all 301'd to a random site.  Screwed traffic for 2 weeks and lost thousands. 

That also happened at the time of a major solar flare...