Passar para o conteúdo principal

Guide to Name Collision Identification and Mitigation for IT Professionals

This content is available only in English Language

Download Now

Guide to Name Collision Identification and Mitigation for IT Professionals (version 1.1) [PDF, 476 KB]

Summary

Name collisions have the potential to create unanticipated results for organizations that use private naming systems. This document lists some of those potential results and specifies best practices for changing the way that other naming systems are used within organizations.

For naming systems that use a string that is becoming (or is already) a TLD in the global DNS, mitigation best comes in the form of migrating to a domain name that is rooted in the global DNS. For naming systems that use name shortening with search lists, mitigation can come only by eliminating the use of search lists. Steps to achieve these mitigations also include long-term monitoring in private networks to be sure that all instances of names that might cause collisions are no longer being used.

The comprehensive mitigation for the problems of name collisions is to use Fully Qualified Domain Names (FQDNs) in all places where a domain name is used. In a network that is already using the global DNS, this means not using search lists. In a network that uses a private naming system, this means migrating to a domain  name rooted in the global DNS, and avoiding the use of search lists.