Global Server Selector
Global Server Selector provides easy configuration and automatically updates DNS for highly available access to distributed applications and services.
Read moreA GUID (globally unique identifier) is a 128-bit value that provides a stable, unique identifier for objects, records, and devices in networked environments where hostnames and IP addresses frequently change. Generated locally using an algorithm without central coordination, GUIDs enable distributed systems and inventory management tools to track objects consistently across name changes, DHCP reassignments, and subnet migrations. Operational challenges arise from cloned virtual machines sharing identical GUIDs, format inconsistencies between systems, and improper handling during directory object rebuilds, requiring careful implementation in enterprise network management and IPAM solutions.
A GUID is created by an algorithm that makes a collision between two independently generated values extremely unlikely. No lookup against a central registry is needed at creation time.
A GUID is a 128-bit value, shown as 32 hexadecimal digits in the pattern 8-4-4-4-12, for example in braces in Windows tools. The format matches the UUID layout in RFC 4122, which defines several versions. Some versions derive the value from a timestamp and a node identifier, some from a name hashed with a namespace, and one from random numbers. Version 4 relies on random bits, so uniqueness is statistical rather than guaranteed. With 122 random bits in a version 4 value, the chance of two matching values is negligible at practical scale. Once generated, the GUID is stored as an attribute on the object, such as a directory entry, a database row or a device record. Applications then refer to the object by that value, so the object keeps its identity even when its name, address or location changes. This is what separates a GUID from a hostname or IP address, which can change over time.
When an integration matches objects by hostname or IP address instead of GUID, a rename or DHCP lease change creates a duplicate record or orphans the original. Using the GUID as the join key avoids this.
Deleting and recreating a directory object produces a new GUID even if the name is identical. Group memberships, permissions and linked records that referenced the old GUID no longer resolve.
Braces, upper or lower case and missing hyphens differ between tools. String comparisons then fail for what is the same value, so imports and lookups should normalize the format first.
Version 4 values depend on a good random generator. A weak or identically seeded source, as can occur in freshly cloned systems, raises the chance of duplicates well above the theoretical level.