Alternatives to CoreDNS logo

Alternatives to CoreDNS

SkyDNS, Consul, PowerDNS, BIND9, and Istio are the most popular alternatives and competitors to CoreDNS.
51
67
+ 1
5

What is CoreDNS and what are its top alternatives?

CoreDNS is a flexible, extensible DNS server written in Go, designed with the cloud-native ecosystem in mind. It supports CoreDNS support multiple backends, including etcd, Kubernetes, and Prometheus. However, CoreDNS can lack some advanced features found in traditional DNS servers.

  1. Bind: BIND (Berkeley Internet Name Domain) is a widely used open-source DNS server software. It is known for its stability and extensive feature set, making it suitable for complex DNS configurations. However, setting up and maintaining BIND can be more complex compared to CoreDNS.

  2. Unbound: Unbound is a validating, recursive, and caching DNS resolver designed for high performance. It is known for its security features and minimal resource usage. However, Unbound may not offer the same level of flexibility as CoreDNS in terms of plugin support.

  3. PowerDNS: PowerDNS is an open-source DNS server software known for its scalability and modular design. It offers support for various backends and features like DNSSEC and geo-routing. However, PowerDNS may have a steeper learning curve compared to CoreDNS due to its more advanced features.

  4. Knot DNS: Knot DNS is a high-performance authoritative DNS server with support for DNSSEC. It is designed for reliability and scalability, making it suitable for enterprise environments. However, Knot DNS may lack some of the cloud-native integrations offered by CoreDNS.

  5. dnsmasq: Dnsmasq is a lightweight DNS forwarder and DHCP server known for its simplicity and ease of use. It is commonly used for local network configurations and small-scale deployments. However, dnsmasq may not offer the same level of extensibility as CoreDNS.

  6. Yadifa: Yadifa is a lightweight authoritative DNS server designed for high performance and scalability. It is suitable for managing large domain infrastructures efficiently. However, Yadifa may lack some of the customization options available in CoreDNS through plugins.

  7. MaraDNS: MaraDNS is a security-focused DNS server known for its simplicity and minimalistic design. It emphasizes security and ease of configuration, making it suitable for basic DNS requirements. However, MaraDNS may lack some advanced features present in CoreDNS.

  8. Acrylic DNS Proxy: Acrylic DNS Proxy is a local DNS proxy server optimized for Windows systems. It offers caching and filtering capabilities, making it useful for improving network performance and security. However, Acrylic DNS Proxy may not offer the same level of extensibility as CoreDNS.

  9. Dnsmasq: Dnsmasq is a lightweight DNS forwarder and DHCP server known for its simplicity and ease of use. It is commonly used for local network configurations and small-scale deployments. However, dnsmasq may not offer the same level of extensibility as CoreDNS.

  10. SimpleDNS Plus: SimpleDNS Plus is a Windows-based DNS server software known for its user-friendly interface and comprehensive feature set. It offers support for DNSSEC, dynamic updates, and advanced filtering options. However, SimpleDNS Plus may lack some of the cloud-native integrations present in CoreDNS.

Top Alternatives to CoreDNS

  • SkyDNS
    SkyDNS

    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). ...

  • Consul
    Consul

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

  • PowerDNS
    PowerDNS

    It features a large number of different backends ranging from simple BIND style zonefiles to relational databases and load balancing/failover algorithms. A DNS recursor is provided as a separate program. ...

  • BIND9
    BIND9

    It is a versatile name server software. It has evolved to be a very flexible, full-featured DNS system. Whatever your application is, it probably has the required features. ...

  • Istio
    Istio

    Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc. ...

  • Traefik
    Traefik

    A modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Traefik integrates with your existing infrastructure components and configures itself automatically and dynamically. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

CoreDNS alternatives & related posts

SkyDNS logo

SkyDNS

8
23
2
Distributed service for announcement and discovery of services
8
23
+ 1
2
PROS OF SKYDNS
  • 2
    Srv discovery for etcd
CONS OF SKYDNS
    Be the first to leave a con

    related SkyDNS posts

    Consul logo

    Consul

    1.1K
    1.5K
    213
    A tool for service discovery, monitoring and configuration
    1.1K
    1.5K
    + 1
    213
    PROS OF CONSUL
    • 61
      Great service discovery infrastructure
    • 35
      Health checking
    • 29
      Distributed key-value store
    • 26
      Monitoring
    • 23
      High-availability
    • 12
      Web-UI
    • 10
      Token-based acls
    • 6
      Gossip clustering
    • 5
      Dns server
    • 4
      Not Java
    • 1
      Docker integration
    • 1
      Javascript
    CONS OF CONSUL
      Be the first to leave a con

      related Consul posts

      John Kodumal

      As we've evolved or added additional infrastructure to our stack, we've biased towards managed services. Most new backing stores are Amazon RDS instances now. We do use self-managed PostgreSQL with TimescaleDB for time-series data—this is made HA with the use of Patroni and Consul.

      We also use managed Amazon ElastiCache instances instead of spinning up Amazon EC2 instances to run Redis workloads, as well as shifting to Amazon Kinesis instead of Kafka.

      See more
      Shared insights
      on
      ConsulConsulElixirElixirErlangErlang
      at

      Postmates built a tool called Bazaar that helps onboard new partners and handles several routine tasks, like nightly emails to merchants alerting them about items that are out of stock.

      Since they ran Bazaar across multiple instances, the team needed to avoid sending multiple emails to their partners by obtaining lock across multiple hosts. To solve their challenge, they created and open sourced ConsulMutEx, and an Elixir module for acquiring and releasing locks with Consul and other backends.

      It works with Consul’s KV store, as well as other backends, including ets, Erlang’s in-memory database.

      See more
      PowerDNS logo

      PowerDNS

      39
      50
      0
      A DNS server, written in C++ and runs on most Unix derivatives
      39
      50
      + 1
      0
      PROS OF POWERDNS
        Be the first to leave a pro
        CONS OF POWERDNS
          Be the first to leave a con

          related PowerDNS posts

          BIND9 logo

          BIND9

          53
          52
          0
          A software for translating domain names into IP addresses
          53
          52
          + 1
          0
          PROS OF BIND9
            Be the first to leave a pro
            CONS OF BIND9
              Be the first to leave a con

              related BIND9 posts

              Istio logo

              Istio

              941
              1.5K
              54
              Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft
              941
              1.5K
              + 1
              54
              PROS OF ISTIO
              • 14
                Zero code for logging and monitoring
              • 9
                Service Mesh
              • 8
                Great flexibility
              • 5
                Resiliency
              • 5
                Powerful authorization mechanisms
              • 5
                Ingress controller
              • 4
                Easy integration with Kubernetes and Docker
              • 4
                Full Security
              CONS OF ISTIO
              • 16
                Performance

              related Istio posts

              Shared insights
              on
              IstioIstioDaprDapr

              At my company, we are trying to move away from a monolith into microservices led architecture. We are now stuck with a problem to establish a communication mechanism between microservices. Since, we are planning to use service meshes and something like Dapr/Istio, we are not sure on how to split services between the two. Service meshes offer Traffic Routing or Splitting whereas, Dapr can offer state management and service-service invocation. At the same time both of them provide mLTS, Metrics, Resiliency and tracing. How to choose who should offer what?

              See more
              Anas MOKDAD
              Shared insights
              on
              KongKongIstioIstio

              As for the new support of service mesh pattern by Kong, I wonder how does it compare to Istio?

              See more
              Traefik logo

              Traefik

              828
              1.2K
              93
              The Cloud Native Edge Router
              828
              1.2K
              + 1
              93
              PROS OF TRAEFIK
              • 20
                Kubernetes integration
              • 18
                Watch service discovery updates
              • 14
                Letsencrypt support
              • 13
                Swarm integration
              • 12
                Several backends
              • 6
                Ready-to-use dashboard
              • 4
                Easy setup
              • 4
                Rancher integration
              • 1
                Mesos integration
              • 1
                Mantl integration
              CONS OF TRAEFIK
              • 7
                Not very performant (fast)
              • 7
                Complicated setup

              related Traefik posts

              Gabriel Pa
              Shared insights
              on
              TraefikTraefikNGINXNGINX
              at

              We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.

              We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job

              The biggest win for naologic was the ability to set dynamic configurations without having to restart the server

              See more
              Howie Zhao
              Full Stack Engineer at yintrust · | 6 upvotes · 124K views
              Shared insights
              on
              cookiecuttercookiecutterTraefikTraefik
              at

              We use Traefik as the web server.

              The reasons for choosing Traefik over Nginx are as follows:

              • Traefik built-in Let’s Encrypt and supports automatic renewal
              • Traefik automatically enables HTTP/2
              • Prometheus can be supported through simple Traefik configuration
              • cookiecutter django integrates Traefik's configuration by default
              See more
              JavaScript logo

              JavaScript

              351K
              267.3K
              8.1K
              Lightweight, interpreted, object-oriented language with first-class functions
              351K
              267.3K
              + 1
              8.1K
              PROS OF JAVASCRIPT
              • 1.7K
                Can be used on frontend/backend
              • 1.5K
                It's everywhere
              • 1.2K
                Lots of great frameworks
              • 896
                Fast
              • 745
                Light weight
              • 425
                Flexible
              • 392
                You can't get a device today that doesn't run js
              • 286
                Non-blocking i/o
              • 237
                Ubiquitousness
              • 191
                Expressive
              • 55
                Extended functionality to web pages
              • 49
                Relatively easy language
              • 46
                Executed on the client side
              • 30
                Relatively fast to the end user
              • 25
                Pure Javascript
              • 21
                Functional programming
              • 15
                Async
              • 13
                Full-stack
              • 12
                Its everywhere
              • 12
                Future Language of The Web
              • 12
                Setup is easy
              • 11
                JavaScript is the New PHP
              • 11
                Because I love functions
              • 10
                Like it or not, JS is part of the web standard
              • 9
                Expansive community
              • 9
                Can be used in backend, frontend and DB
              • 9
                Easy
              • 9
                Everyone use it
              • 8
                Most Popular Language in the World
              • 8
                Can be used both as frontend and backend as well
              • 8
                Powerful
              • 8
                For the good parts
              • 8
                No need to use PHP
              • 8
                Easy to hire developers
              • 7
                Love-hate relationship
              • 7
                Agile, packages simple to use
              • 7
                Its fun and fast
              • 7
                Hard not to use
              • 7
                Nice
              • 7
                Versitile
              • 7
                Evolution of C
              • 7
                Photoshop has 3 JS runtimes built in
              • 7
                It's fun
              • 7
                Popularized Class-Less Architecture & Lambdas
              • 7
                Supports lambdas and closures
              • 6
                Can be used on frontend/backend/Mobile/create PRO Ui
              • 6
                1.6K Can be used on frontend/backend
              • 6
                Client side JS uses the visitors CPU to save Server Res
              • 6
                It let's me use Babel & Typescript
              • 6
                Easy to make something
              • 5
                What to add
              • 5
                Clojurescript
              • 5
                Stockholm Syndrome
              • 5
                Function expressions are useful for callbacks
              • 5
                Scope manipulation
              • 5
                Everywhere
              • 5
                Client processing
              • 5
                Promise relationship
              • 4
                Because it is so simple and lightweight
              • 4
                Only Programming language on browser
              • 1
                Easy to learn
              • 1
                Not the best
              • 1
                Hard to learn
              • 1
                Easy to understand
              • 1
                Test
              • 1
                Test2
              • 1
                Subskill #4
              • 0
                Hard 彤
              CONS OF JAVASCRIPT
              • 22
                A constant moving target, too much churn
              • 20
                Horribly inconsistent
              • 15
                Javascript is the New PHP
              • 9
                No ability to monitor memory utilitization
              • 8
                Shows Zero output in case of ANY error
              • 7
                Thinks strange results are better than errors
              • 6
                Can be ugly
              • 3
                No GitHub
              • 2
                Slow

              related JavaScript posts

              Zach Holman

              Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

              But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

              But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

              Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

              See more
              Conor Myhrvold
              Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 10.1M views

              How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

              Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

              Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

              https://eng.uber.com/distributed-tracing/

              (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

              Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

              See more
              Git logo

              Git

              289.9K
              174.3K
              6.6K
              Fast, scalable, distributed revision control system
              289.9K
              174.3K
              + 1
              6.6K
              PROS OF GIT
              • 1.4K
                Distributed version control system
              • 1.1K
                Efficient branching and merging
              • 959
                Fast
              • 845
                Open source
              • 726
                Better than svn
              • 368
                Great command-line application
              • 306
                Simple
              • 291
                Free
              • 232
                Easy to use
              • 222
                Does not require server
              • 27
                Distributed
              • 22
                Small & Fast
              • 18
                Feature based workflow
              • 15
                Staging Area
              • 13
                Most wide-spread VSC
              • 11
                Role-based codelines
              • 11
                Disposable Experimentation
              • 7
                Frictionless Context Switching
              • 6
                Data Assurance
              • 5
                Efficient
              • 4
                Just awesome
              • 3
                Github integration
              • 3
                Easy branching and merging
              • 2
                Compatible
              • 2
                Flexible
              • 2
                Possible to lose history and commits
              • 1
                Rebase supported natively; reflog; access to plumbing
              • 1
                Light
              • 1
                Team Integration
              • 1
                Fast, scalable, distributed revision control system
              • 1
                Easy
              • 1
                Flexible, easy, Safe, and fast
              • 1
                CLI is great, but the GUI tools are awesome
              • 1
                It's what you do
              • 0
                Phinx
              CONS OF GIT
              • 16
                Hard to learn
              • 11
                Inconsistent command line interface
              • 9
                Easy to lose uncommitted work
              • 7
                Worst documentation ever possibly made
              • 5
                Awful merge handling
              • 3
                Unexistent preventive security flows
              • 3
                Rebase hell
              • 2
                When --force is disabled, cannot rebase
              • 2
                Ironically even die-hard supporters screw up badly
              • 1
                Doesn't scale for big data

              related Git posts

              Simon Reymann
              Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 9.3M views

              Our whole DevOps stack consists of the following tools:

              • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
              • Respectively Git as revision control system
              • SourceTree as Git GUI
              • Visual Studio Code as IDE
              • CircleCI for continuous integration (automatize development process)
              • Prettier / TSLint / ESLint as code linter
              • SonarQube as quality gate
              • Docker as container management (incl. Docker Compose for multi-container application management)
              • VirtualBox for operating system simulation tests
              • Kubernetes as cluster management for docker containers
              • Heroku for deploying in test environments
              • nginx as web server (preferably used as facade server in production environment)
              • SSLMate (using OpenSSL) for certificate management
              • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
              • PostgreSQL as preferred database system
              • Redis as preferred in-memory database/store (great for caching)

              The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

              • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
              • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
              • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
              • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
              • Scalability: All-in-one framework for distributed systems.
              • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
              See more
              Tymoteusz Paul
              Devops guy at X20X Development LTD · | 23 upvotes · 8.3M views

              Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

              It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

              I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

              We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

              If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

              The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

              Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

              See more