Alternatives to CoreDNS logo

Alternatives to CoreDNS

SkyDNS, Consul, PowerDNS, BIND9, and Istio are the most popular alternatives and competitors to CoreDNS.
27
37
+ 1
4

What is CoreDNS and what are its top alternatives?

CoreDNS is a DNS server. It is written in Go. It can be used in a multitude of environments because of its flexibility
CoreDNS is a tool in the DNS Management category of a tech stack.
CoreDNS is an open source tool with 6.9K GitHub stars and 1.2K GitHub forks. Here’s a link to CoreDNS's open source repository on GitHub

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

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

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

CoreDNS alternatives & related posts

SkyDNS logo

SkyDNS

8
14
1
Distributed service for announcement and discovery of services
8
14
+ 1
1
PROS OF SKYDNS
CONS OF SKYDNS
    No cons available

    related SkyDNS posts

    Consul logo

    Consul

    889
    1K
    198
    A tool for service discovery, monitoring and configuration
    889
    1K
    + 1
    198

    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

    Since the beginning, Cal Henderson has been the CTO of Slack. Earlier this year, he commented on a Quora question summarizing their current stack.

    Apps
    • Web: a mix of JavaScript/ES6 and React.
    • Desktop: And Electron to ship it as a desktop application.
    • Android: a mix of Java and Kotlin.
    • iOS: written in a mix of Objective C and Swift.
    Backend
    • The core application and the API written in PHP/Hack that runs on HHVM.
    • The data is stored in MySQL using Vitess.
    • Caching is done using Memcached and MCRouter.
    • The search service takes help from SolrCloud, with various Java services.
    • The messaging system uses WebSockets with many services in Java and Go.
    • Load balancing is done using HAproxy with Consul for configuration.
    • Most services talk to each other over gRPC,
    • Some Thrift and JSON-over-HTTP
    • Voice and video calling service was built in Elixir.
    Data warehouse
    • Built using open source tools including Presto, Spark, Airflow, Hadoop and Kafka.
    Etc
    See more
    PowerDNS logo

    PowerDNS

    23
    24
    0
    A DNS server, written in C++ and runs on most Unix derivatives
    23
    24
    + 1
    0
    PROS OF POWERDNS
      No pros available
      CONS OF POWERDNS
        No cons available

        related PowerDNS posts

        BIND9 logo

        BIND9

        31
        20
        0
        A software for translating domain names into IP addresses
        31
        20
        + 1
        0
        PROS OF BIND9
          No pros available
          CONS OF BIND9
            No cons available

            related BIND9 posts

            Istio logo

            Istio

            507
            881
            40
            Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft
            507
            881
            + 1
            40

            related Istio posts

            Anas MOKDAD
            Shared insights
            on
            Kong
            Istio

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

            See more

            related Traefik posts

            Gabriel Pa
            Shared insights
            on
            Traefik
            NGINX
            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
            Shared insights
            on
            Envoy
            HAProxy
            Traefik
            NGINX

            We are looking to configure a load balancer with some admin UI. We are currently struggling to decide between NGINX, Traefik, HAProxy, and Envoy. We will use a load balancer in a containerized environment and the load balancer should flexible and easy to reload without changes in case containers are scaled up.

            See more

            related Amazon Route 53 posts

            Ganesa Vijayakumar
            Full Stack Coder | Module Lead · | 18 upvotes · 1.9M views

            I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

            I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

            As per my work experience and knowledge, I have chosen the followings stacks to this mission.

            UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

            Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

            Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

            Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

            Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

            Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

            Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

            Happy Coding! Suggestions are welcome! :)

            Thanks, Ganesa

            See more
            Bram Verdonck

            Yesterday we moved away from using CloudFlare towards Amazon Route 53 for a few reasons. Although CloudFlare is a great platform, once you reach almost a 100% AWS Service integration, it makes it hard to still use CloudFlare in the stack. Also being able to use Aliases for DNS makes it faster because instead of doing a CNAME and an A record lookup, you will be able to receive the A records from the end services directly. We always loved working with CloudFlare , especially for DNS as we already used Amazon CloudFront for CDN. But having everything within AWS makes it "cleaner" when deploying automatically using AWS CloudFormation. All that aside, the main reason for moving towards Amazon Route 53 for DNS is the ability to do geolocation and latency based DNS responses. Doing this outside the AWS console would increase the complexity.

            See more
            DNS Made Easy logo

            DNS Made Easy

            2.6K
            55
            18
            DNS performance, reliability, and security have never been easier.
            2.6K
            55
            + 1
            18
            CONS OF DNS MADE EASY
              No cons available

              related DNS Made Easy posts