A couple years ago, a customer had TMG on Hyper-V and from time to time it quit responding. A reboot brought it back to life, but with dozens of users, and highly burstful activity, it would occassionally quit responding again. A call to tech support immediately identified the situation as being unique to TMG on Hyper-V. It turns out that heavy bursts on TMG in this situation would cause delays in referencing the internal DNS and cause sufficient traffic that it falsely detected a host block situation (I recall it blocked the internal DNS server?). In any event, they walked me through setting up a second DNS server on TMG, allowing TMG to reference its own DNS server. It fixed the problem.
I've not found any document, white-paper, or step-by-step guide that covers all the territory we covered in that tech support phone call. As I recall, the solution involved creating a stub to the internal DNS server, a change in forwarding, a reverse DNS setup, and a change in NIC DNS settings. Tech support quickly identified the problem and quickly walked me through the solution, leading me to believe such a document exists.
I have a new customer facing the same situation. Can you point me to a procedure that discusses this situation and provides a step-by-step guide to setting up a second DNS server on TMG? thank you.
Beware of unmoderated moderators in the Expression Web forums.