StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. API Tools
  4. Service Discovery
  5. CoreDNS vs SkyDNS

CoreDNS vs SkyDNS

OverviewComparisonAlternatives

Overview

SkyDNS
SkyDNS
Stacks8
Followers23
Votes2
GitHub Stars2.2K
Forks304
CoreDNS
CoreDNS
Stacks48
Followers68
Votes5
GitHub Stars13.5K
Forks2.3K

CoreDNS vs SkyDNS: What are the differences?

Introduction:

In this document, we will explore the key differences between CoreDNS and SkyDNS. Both CoreDNS and SkyDNS are DNS servers that provide DNS resolution within Kubernetes clusters. However, there are several distinct differences between the two. Let's dive into the details.

  1. Architecture and Implementation: CoreDNS is a pluggable DNS server that uses plugins to customize its behavior, making it highly flexible and extensible. It allows easy integration of external data sources, such as databases or APIs. On the other hand, SkyDNS is a full-featured DNS server that is specifically designed for Kubernetes. It relies on etcd, a distributed key-value store, to store the DNS information for the cluster.

  2. Scalability and Performance: CoreDNS is built with performance and scalability in mind. It is highly optimized to handle large-scale deployments and can process a high volume of DNS queries efficiently. SkyDNS, on the other hand, has some scalability limitations due to its reliance on etcd for storing the DNS information. As the cluster size increases, it may put more load on the etcd cluster and impact the overall performance.

  3. Configuration and Flexibility: CoreDNS offers a wide range of configuration options through its plugins. Administrators can easily customize the DNS behavior by enabling or disabling plugins and configuring their settings. SkyDNS, on the other hand, has limited configuration options compared to CoreDNS. It follows a more opinionated approach with minimal configuration needed, which can be beneficial for simpler deployments but may limit flexibility in complex scenarios.

  4. Community and Support: CoreDNS has a larger and more active community compared to SkyDNS. It is an official Cloud Native Computing Foundation (CNCF) project and is widely adopted within the Kubernetes ecosystem. This leads to better community support, frequent updates, and a larger pool of resources and documentation available. SkyDNS, on the other hand, has a smaller community and may not have the same level of support and resources as CoreDNS.

  5. Compatibility and Integration: CoreDNS is designed to be a drop-in replacement for existing DNS servers in Kubernetes, making it highly compatible with existing setups. It seamlessly integrates with Kubernetes and can be easily configured to replace the default DNS resolver. SkyDNS, on the other hand, is specifically built for Kubernetes and tightly integrated with the platform. While it may offer better compatibility within the Kubernetes ecosystem, it may not be as easily portable to other environments.

  6. Adoption and Maturity: CoreDNS has gained significant traction in the industry and is widely recognized as the recommended DNS server for Kubernetes. It is considered more mature and stable compared to SkyDNS, which has a smaller user base and may be perceived as less battle-tested. This higher adoption rate and maturity level of CoreDNS make it a safer choice for production deployments.

In summary, CoreDNS offers greater flexibility, scalability, community support, and compatibility, making it the preferred choice for most Kubernetes deployments. SkyDNS, on the other hand, focuses on simplicity, easy integration with Kubernetes, but may have limitations in terms of scalability and advanced configuration.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

SkyDNS
SkyDNS
CoreDNS
CoreDNS

SkyDNS is a distributed service for announcement and discovery of services. It leverages Raft for high-availability and consensus, and utilizes DNS queries to discover available services. This is done by leveraging SRV records in DNS, with special meaning given to subdomains, priorities and weights (more info here: http://blog.gopheracademy.com/skydns).

CoreDNS is a DNS server. It is written in Go. It can be used in a multitude of environments because of its flexibility

You announce your service by submitting JSON over HTTP to SkyDNS with information about your service. This information will then be available for queries either via DNS or HTTP.;SkyDNS requires that services submit an HTTP request to update their TTL within the TTL they last supplied. If the service fails to do so within this timeframe SkyDNS will expire the service automatically. This will allow for nodes to fail and DNS to reflect this quickly.;You can find services by querying SkyDNS via any DNS client or utility. It uses a known domain syntax with wildcards to find matching services.
Plugins; Service Discovery; Fast and Flexible
Statistics
GitHub Stars
2.2K
GitHub Stars
13.5K
GitHub Forks
304
GitHub Forks
2.3K
Stacks
8
Stacks
48
Followers
23
Followers
68
Votes
2
Votes
5
Pros & Cons
Pros
  • 2
    Srv discovery for etcd
Pros
  • 3
    Kubernetes Integration
  • 2
    Open Soure

What are some alternatives to SkyDNS, CoreDNS?

Amazon Route 53

Amazon Route 53

Amazon Route 53 is designed to give developers and businesses an extremely reliable and cost effective way to route end users to Internet applications by translating human readable names like www.example.com into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other. Route 53 effectively connects user requests to infrastructure running in Amazon Web Services (AWS) – such as an Amazon Elastic Compute Cloud (Amazon EC2) instance, an Amazon Elastic Load Balancer, or an Amazon Simple Storage Service (Amazon S3) bucket – and can also be used to route users to infrastructure outside of AWS.

Consul

Consul

Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.

DNSimple

DNSimple

DNSimple provides the tools you need to manage your domains. We offer both a carefully crafted web interface for managing your domains and DNS records, as well as an HTTP API with various code libraries and tools. Buy, connect, operate!

Eureka

Eureka

Eureka is a REST (Representational State Transfer) based service that is primarily used in the AWS cloud for locating services for the purpose of load balancing and failover of middle-tier servers.

Google Cloud DNS

Google Cloud DNS

Use Google's infrastructure for production quality, high volume DNS serving. Your users will have reliable, low-latency access to Google's infrastructure from anywhere in the world using our network of Anycast name servers.

Zookeeper

Zookeeper

A centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications.

Dyn

Dyn

An all-in-one Managed DNS service for your registered domain names. Dyn DNS is the perfect solution for your domain name’s DNS needs, whether it is for personal or business use. It gives you complete control over your DNS zone and its associated DNS records, complete with a simple DNS management web interface.

etcd

etcd

etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines. It’s open-source and available on GitHub. etcd gracefully handles master elections during network partitions and will tolerate machine failure, including the master.

DNS Made Easy

DNS Made Easy

DNS Made Easy is a subsidiary of Tiggee LLC, and is a world leader in providing global IP Anycast enterprise DNS services. DNS Made Easy is currently ranked the fastest provider for 8 consecutive months and the most reliable provider.

NS1

NS1

NS1’s intelligent DNS & traffic management platform, with its data driven architecture and unique Filter Chain routing engine, is purpose-built for the most demanding, mission-critical applications on the Internet.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

Postman
Swagger UI

Postman vs Swagger UI

gulp
Grunt

Grunt vs Webpack vs gulp