Topic starter
23/06/2026 7:04 pm
TL;DR: A Denver point of presence has been added to DNS Made Easy and Constellix DNS, bringing the network to 24 global DNS PoPs and 550 Gbps of total peer capacity, with reported Colorado speed improvement from 18.78 ms to 15.39 ms, according to DigiCert. The governance lesson is that routing resilience and availability are operational identity-adjacent concerns, because DNS remains a control plane dependency for access, trust, and service reachability.
Editorial analysis by NHI Mgmt Group, based on content published by DigiCert: “DigiCert DNS Made Easy Announces New Denver Point of Presence”.
By the numbers:
- The Denver deployment is the 24th global DNS PoP in DigiCert's network.
- The Denver point of presence adds 10 Gbps of peering to AS16552.
- AS16552 total peer capacity now stands at 550 Gbps.
Key questions
Q: How should teams govern DNS records that support identity and trust controls?
A: Security teams should classify DNS records by the trust function they support, not only by technical type.
Q: Why does DNS performance matter to identity and access programmes?
A: DNS performance matters because users and services must resolve names before they can authenticate, connect, or exchange tokens.
Q: What breaks when DNS routing becomes unstable in a global environment?
A: Resolution failures can cascade into apparent login outages, certificate validation problems, and unreachable applications.
Practitioner guidance
- Map DNS dependencies across access journeys Identify which login pages, certificate services, federation endpoints, and customer-facing applications rely on DNS resolution before access can succeed.
- Test regional routing and failover behaviour Run resilience tests that measure lookup latency, resolution success, and service reachability during regional degradation or upstream path loss.
- Set availability thresholds for trust services Define acceptable DNS performance and uptime for services that support authentication, certificate validation, and application entry points.
Bottom line: DNS availability is an access-path issue as much as a network issue, because identity journeys depend on name resolution before policy enforcement can begin.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 2:52 am
DNS resilience belongs inside identity governance because access cannot be governed if name resolution is unstable. Identity programmes depend on users, services, and trust endpoints reaching the right destination at the right time. When DNS becomes slow or unavailable, the access path fails before policy enforcement can even begin, which makes availability a governance issue rather than a pure infrastructure metric.
A question worth separating out:
Q: What should teams do when DNS is a hidden dependency for access?
A: They should build a dependency map that shows which services rely on DNS before authentication or trust checks can occur, then assign incident ownership accordingly. If the access path cannot tolerate DNS degradation, the problem is not only technical redundancy. It is also a governance gap in how availability responsibilities are defined.
👉 Read our full editorial: DigiCert DNS Made Easy expands Denver presence for DNS resilience