SolarWinds Knowledge Base

• http://www.microsoft.com/technet/security/advisory/971888.mspx
• http://support.microsoft.com/kb/957579

• Customers whose domain name has three or more labels, such as "contoso.co.us",
• Customers who do not have a DNS suffix list configured, or
• Customers for whom the following mitigating factors do not apply.

• Customers who are joined to a domain and have a DNS suffix search list configured on their system are not at risk of inadvertently treating external systems as though they were internal. Microsoft encourages all enterprise customers to set DNS suffix search lists on client systems in order to ensure all DNS queries stay within organizational boundaries.
• In most cases, home users who are not members of a domain do not use DNS devolution and therefore are not exposed to this risk. Home users who are not members of a domain but have configured a primary DNS suffix, however, do use DNS devolution and are at risk of inadvertently treating external systems as though they were internal.
• Customers whose DNS domain name consists of two labels are not exposed to this risk. An example of a customer who is not affected is contoso.com or fabrikam.gov, where "contoso" and "fabrikam" are customer registered domain names under their respective ".com" and ".gov" top-level domains (TLDs).

There is no indication that this update to DNS Devolution should affect Orion users

This article applies to:

• Orion NPM 10.1.1
• Orion NPM 10.1