Strange DNS events

Today at around 3PM pacific all systems reported a DNS timeout resolving teamviewer.com addresses.  The problem appeared to lockup all dns servers with some kind of massive DNS storm from all teamviewer clients to all our internal DNS servers.

Is this potentially a known issue caused by agent options, something we're doing or perhaps are there other known causes?

The problem occured today, yesterday and on the 23'rd around the same time.  There is a few other instances on the 18'th at 6am, the 6'th at 10:30am and again on the 1'st at 3pm.

 It's just really wierd, out of many thousands of lookups going on continuously, we're only getting teamviewer dns timeout warnings all at the same time and to different teamviewer.com subdomains.