2.1.0 • Public • Published


Concordant is a DNS resolver module for those involved in microservice development. For best results concordant should be used with the Fuge microservice shell and Kubernetes. See:

If you're using this module, and need help, you can:


To install Concordant use npm:

$ npm install --save concordant


Service discovery is a key problem to address when developing a microservice system. Typically there will be many services and pieces of infrastructure such as databases and queueing systems that need to be located and consumed. Usually the local development topology will be significantly different from the production environment which will be different again from any QA or staging environment.

The traditional approach to solving these issues is to supply a configuration file and to use this to connect services with well known port numbers.

Concordant takes a different approach. When a specific environment variable is set (DNS_HOST) concordant will perform service discovery lookups against this host directly. If not defined it will use the system configured DNS resolution. This is useful because it means that we can run a simple DNS server in development that mimics how our production environment behaves. This significantly reduces configuration overhead and friction.

Concordant performs DNS based SRV and, optionally, A record lookups in order to determine the port number and IP address for a given service. It uses the following simple algorithm:

  • if the environment variable DNS_HOST is set then perform lookups directly against this host
  • otherwise use the system DNS configuration to perform lookups
  • depending on the value of the environment variable DNS_MODE, concordant will lookup SRV and/or A records
  • if DNS_MODE is 'SRV' then for each lookup first perform an SRV query to obtain a port number and name. The name can then optionally be resolved fully to determine an IP address
  • Otherwise if DNS_MODE is 'A' just perform and A query in order to resolve the IP address for a hostname

Kubernetes DNS and Fuge

Kubernetes supplies DNS records of the following form for service discovery:

  • SRV
  • A

So a consumer of a service need only know the service and port name in order to discover a service within a given namespace. Concordant will perform these queries. For example, given that we have a redis container in our system with service name redis and port name main in namespace mynamespace, we can use concordant as follows:

var redis = require('redis')
var concordant = require('concordant')()
// Change 'resolve' to 'resolveSrv' to resolve the host and port without performing the A lookup to resolve IP addresses
concordant.dns.resolve('_main._tcp.redis.mynamespace.svc.cluster.local', function (err, results) {
  if (err) { return cb(err) }
    var client = redis.createClient({host: results[0].host, port: results[0].port})    
    // do stuff with redis...

The fuge development shell will supply the exact same DNS records. Code that uses concordant for discovery will run unchanged in a development or production environment. i.e. the above sample will run unchanged in the Fuge development shell and within a Kubernetes environment.


Full resolution

Require the module and call dns.resolve. Callback contains an array of results or err. Results in the form:

[{host: '', port: 1234},
 {host: '', port: 1235}]

Hostname resolution (SRV lookup only)

Require the module and call dns.resolveSrv. Callback contains an array of results or err. Results in the form:

[{host: 'service.namespace.svc.cluster.local', port: 1234},
 {host: 'service.namespace.svc.cluster.local', port: 1235}]

Example SRV lookup

var concordant = require('concordant')()
concordant.dns.resolveSrv('', function (err, results) {
  if (err) { return cb(err) }
    // connect to results[0].host results[0].port and do stuff...

Example A lookup

var concordant = require('concordant')()
concordant.dns.resolve('', function (err, results) {
  if (err) { return cb(err) }
    // connect to results[0].host and do stuff, in this case no port value is returned...

Environment Variables

Concordant uses the following environment variables:

  • DNS_HOST - the DNS host to perform lookup against. If not set use the system supplied DNS configuration
  • DNS_PORT - the DNS port to use. Defaults to 50353 if DNS_HOST is set, otherwise uses the system supplied DNS configuration
  • DNS_MODE - the lookup mode to use, if set to 'A' then perform host only lookup up. If set to 'SRV' perform SRV and A queries to resolve both host and port number. Defaults to 'SRV'


The [apparatus team][] encourage open participation. If you feel you can help in any way, be it with documentation, examples, extra testing, or new features please get in touch.


Copyright the apparatus team 2016, Licensed under MIT.


DownloadsWeekly Downloads






Unpacked Size

29.8 kB

Total Files


Last publish


  • eoinsha
  • pelger