- Qwilt uses CoreDNS in production, implementing a global DNS service allowing access to our ISP edge and regional locations.
- Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
- Sky Betting & Gaming uses CoreDNS for Kubernetes cluster DNS.
- Kismia uses CoreDNS for Kubernetes cluster DNS.
- Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
- Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
- seansean2 uses CoreDNS in production at MIT for DNS.
- Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
- SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
- Z Lab uses CoreDNS in production combination with Consul and Kubernetes Clusters.
- Serpro/estaleiro uses CoreDNS as Kubernetes' DNS Server, in production with tuned Kubernetes plugin options
- Lumo uses CoreDNS as Kubernetes' DNS Server, in production and lab with default configuration
- Booming Games uses CoreDNS in multiple Kubernetes clusters, with Federation plugin. expect to go into production soon.
- Sodimac uses CoreDNS with Kubernetes in production with default configuration.
- Bose uses CoreDNS with Kubernetes in production on very large cluster (over 250 nodes)
- farmotive uses CoreDNS in Kubernetes using default configuration, in its Lab. Expect to be in production soon.
- Zalando SE uses CoreDNS as Kubernetes' DNS Server, in production.
- Trainline uses CoreDNS along with Kubernetes in production, with a tuned configuration.
- AnchorFree uses CoreDNS within Kubernetes in production, with standard configuration.
- Datacom uses CoreDNS with a tuned configuration for Kubernetes, as production.
- Takealot.com uses CoreDNS as Kubernetes' DNS Server, in production.
- scalable minds uses CoreDNS with default configuration for Kubernetes in its production environment.
- ObjectRocket uses CoreDNS on its numerous Kubernetes' clusters, using refined configurations. Address both Lab and Production environment
- Devino Telecom uses CoreDNS with default configuration for Kubernetes for its Lab and its Production.
- Yandex Money uses CoreDNS in Lab and Production, using default configuration for Kubernetes.
- AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
- Skyscanner uses CoreDNS within Kubernetes in production with the configuration tuned to use the Autopath plugin.
- Zinza Technology uses CoreDNS within Kubernetes in production, with standard configuration.
- Hualala uses CoreDNS in Kubernetes using default configuration, in its Lab. Expected to be in production soon.
- Hellofresh uses CoreDNS in multiple Kubernetes clusters, with Forward plugin.
- Render uses CoreDNS in production across all its Kubernetes clusters.
- BackMarket uses CoreDNS within Kubernetes in production, with standard configuration.
- Absa Group uses CoreDNS as an integral part of Kubernetes Global Balancer project - k8gb.
- Northflank uses CoreDNS on all of our Kubernetes clusters across GCP, AWS, and bare-metal.
- PITS Global Data Recovery Services uses CoreDNS on K8s in its highly-loaded internal infrastructure.