DNS.EXE Consuming Hundreds of Ports

[Steve.Stockstill]

We have seen (at a handful of sites) that after restarting their server, a previously available port is now being used by DNS.EXE. This can be troublesome when MobileTM is configured to use this "previously available" port. It's not a showstopper by any means, you simply need to stay away from the range of ports being used.

A bit of research has revealed the answer to this issue and we are not alone in our experiences. Though we are not prepared to make a formal suggestion, we would like to make this information available. The following Microsoft Support Article explains the issue and resolution in detail.

956189 - Some services may not start or may not work correctly on a computer that is running Windows SBS after you install the DNS Server security update 953230 (MS08-037)

http://support.microsoft.com/kb/956189/