<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/performance-and-load-testing-in-identity-management-idm-systems-using-encrypted-dns-edns-and-cor-lgmzaaex5" -->

---
title: Performance and load testing in Identity Management...
description: Performance analysis of Identity Management (IdM) with encrypted DNS (DoT) in OpenShift 4.20 reveals significant throughput differences across protocols....
canonical: https://daily.dev/posts/performance-and-load-testing-in-identity-management-idm-systems-using-encrypted-dns-edns-and-cor-lgmzaaex5
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Performance and load testing in Identity Management (IdM) systems using encrypted DNS (eDNS) and CoreDNS in OpenShift clusters | daily.dev
og:description: Performance analysis of Identity Management (IdM) with encrypted DNS (DoT) in OpenShift 4.20 reveals significant throughput differences across protocols....
og:url: https://daily.dev/posts/performance-and-load-testing-in-identity-management-idm-systems-using-encrypted-dns-edns-and-cor-lgmzaaex5
og:image: https://api.daily.dev/og/posts/lGMZAAex5.png
og:image:alt: Performance and load testing in Identity Management (IdM) systems using encrypted DNS (eDNS) and CoreDNS in OpenShift clusters
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Performance and load testing in Identity Management (IdM) systems using encrypted DNS (eDNS) and CoreDNS in OpenShift clusters

**[Red Hat Developer](https://daily.dev/sources/rhdev)** · 35 min read · 0 upvotes · 0 comments

## Summary

Performance analysis of Identity Management (IdM) with encrypted DNS (DoT) in OpenShift 4.20 reveals significant throughput differences across protocols. Direct resolution achieves 304k QPS with UDP, 253k with TCP (17% drop), and 188k with DoT (37% total drop from UDP). Indirect resolution through CoreDNS caps at 119k QPS regardless of encryption, indicating CoreDNS packet processing is the bottleneck, not TLS overhead. Extensive IdM tuning required disabling BIND logging, increasing TCP client limits to 1000, and enabling kernel busy polling to reach 99% CPU utilization. The hybrid architecture (UDP to CoreDNS, DoT to IdM) adds only 0.17ms median latency versus pure UDP, proving encryption viable with negligible performance impact when properly configured.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://developers.redhat.com/articles/2026/02/16/load-testing-idm-edns-coredns-openshift>

## Similar posts on daily.dev

- [Protect identity infrastructure in cloud-native environments](https://daily.dev/posts/protect-identity-infrastructure-in-cloud-native-environments-3ooefrd27) · Red Hat Developer · 0 upvotes · 0 comments
- [Preventing DNS filtering bypass by Encrypted DNS \(DoT, DoH, DoQ\)](https://daily.dev/posts/preventing-dns-filtering-bypass-by-encrypted-dns-dot-doh-doq--jwbdncedy) · Security Boulevard · 0 upvotes · 0 comments
- [Improving DNS performance with NodeLocalDNS](https://daily.dev/posts/improving-dns-performance-with-nodelocaldns-yudmt2smp) · Neon · 37 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#performance](https://daily.dev/tags/performance), [#kubernetes](https://daily.dev/tags/kubernetes), [#openshift](https://daily.dev/tags/openshift), [#dns](https://daily.dev/tags/dns)

[View this post on daily.dev](https://daily.dev/posts/performance-and-load-testing-in-identity-management-idm-systems-using-encrypted-dns-edns-and-cor-lgmzaaex5)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Performance and load testing in Identity Management (IdM) systems using encrypted DNS (eDNS) and CoreDNS in OpenShift clusters","url":"https://daily.dev/posts/performance-and-load-testing-in-identity-management-idm-systems-using-encrypted-dns-edns-and-cor-lgmzaaex5","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/performance-and-load-testing-in-identity-management-idm-systems-using-encrypted-dns-edns-and-cor-lgmzaaex5"},"datePublished":"2026-02-16T15:16:55.367Z","dateModified":"2026-02-16T15:17:36.897Z","description":"Performance analysis of Identity Management (IdM) with encrypted DNS (DoT) in OpenShift 4.20 reveals significant throughput differences across protocols....","image":"https://developers.redhat.com/sites/default/files/styles/share/public/2020_Coding_Shared_image_A_1.jpg?itok=D9hQKy4J","thumbnailUrl":"https://developers.redhat.com/sites/default/files/styles/share/public/2020_Coding_Shared_image_A_1.jpg?itok=D9hQKy4J","isAccessibleForFree":true,"articleSection":"Red Hat Developer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Red Hat Developer","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/2a8895f3216c4900bdc455585a4ad3e4","url":"https://daily.dev/sources/rhdev"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/performance-and-load-testing-in-identity-management-idm-systems-using-encrypted-dns-edns-and-cor-lgmzaaex5","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,performance,kubernetes,openshift,dns","timeRequired":"PT35M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Red Hat Developer","item":"https://daily.dev/sources/rhdev"},{"@type":"ListItem","position":3,"name":"Performance and load testing in Identity Management (IdM) systems using encrypted DNS (eDNS) and CoreDNS in OpenShift clusters"}]}
```

