dns-nameserver

Nameserver configuration parsers and generators

SYNOPSIS

Name servers have configuration files, and each has its own config file format. This package abstracts the unique implementations into a set of common actions.

nt-ns.js

✗ ./bin/nt-ns.js -h

 +-+-+-+ +-+-+-+-+-+-+-+-+-+-+
 |D|N|S| |N|A|M|E|S|E|R|V|E|R|
 +-+-+-+ +-+-+-+-+-+-+-+-+-+-+

I/O

  -i, --import <bind | knot | maradns | nsd | tinydns>   nameserver type
  -e, --export <bind | knot | maradns | nsd | tinydns>   nameserver type
  -f, --file <file path>                                 source of DNS server config file
  -b, --base <zones dir>                                 path prefix for zone files

Misc

  -v, --verbose    Show status messages during processing
  -h, --help       Display this usage guide

Examples

  1.    ./bin/nt-ns.js -i knot -f ./knot/knot.conf
  2.    ./bin/nt-ns.js -i bind -f ./bind/named.conf -b bind
  3.    ./bin/nt-ns.js -i nsd -f ./nsd/nsd.conf -b nsd -v

  Project home: https://github.com/NicTool/dns-nameserver

FUNCTIONS

getZones

Returns a list of zones (and zone files) from the specified nameserver config file.

parseConfig

Does the heavy lifting for getZones. Accepts a string and returns an object where the keys are DNS zones and the value is the file with that zones resource records.

FEATURES

• config parsers for bind, nsd, knot, maradns, and tinydns

TODO

• config generator
  • bind
  • nsd
  • knot
  • maradns
  • tinydns
  • powerdns (#30)

SEE ALSO

• Dictionary of DNS terms
• Wikipedia, DNS Server Software

DEVELOP

• Conventional Commits
  • fix, feature, BREAKING CHANGE, build, chore, ci, docs, style, test
• keep a changelog