We've got a big SSIS package that imports text files into SQL Server 2005.
The thing ran fine through this massive batch of files on our Dev environment ... then on our next environment up.
On the Test environment, the same package, working against an identical (made from the same script) DB, loading the same files, breaks with errors about the connection being forcibly closed. The breaks appear to occur randomly.
We erroneously thought that a deployment error had caused the problem, so I closed the other question on this: http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/Q_23834194.html
Randy Knight suggested that intermittent DNS failures could be causing the problem. As our dev / BI team talked it through, that was the most reasonable idea to come up.
So ... how do we verify that DNS failures are, or are not, happening in this scenario?