<commit_before># CoreDNS

CoreDNS is DNS server that started as a fork of [Caddy](https://github.com/mholt/caddy/). It has the
same model: it chains middleware.

## Status

Currently CoreDNS is able to:

* Serve zone data from a file, both DNSSEC (NSEC only atm) and DNS is supported.
* Retrieve zone data from primaries, i.e. act as a secondary server.
* Allow for zone transfers, i.e. act as a primary server.
* Use Etcd as a backend, i.e. a 90% replacement for
  [SkyDNS](https://github.com/skynetservices/skydns).
* Serve as a proxy to forward queries to some other (recursive) nameserver.
* Prove metrics (by using Prometheus)
* Rewrite queries (both qtype and qname).
* Provide Logging.

There are corner cases not implement and some blatantly missing functionality; i.e. the secondary
implementation *does not* requery the primary -- *ever*, leading to stale data if the server is
not restarted.

But all in all, CoreDNS should already be able to provide you with enough functionality to replace
parts of BIND9, Knot, NSD or PowerDNS.

CoreDNS is still in the early stages of development and should **not** be used on production servers
yet. For now most documentation is in the source and some blog articles can be [found
here](https://miek.nl/tags/coredns/). If you do want to use CoreDNS in production, please let us
know and how we can help.
<commit_msg>Add text about the test server<commit_after># CoreDNS

CoreDNS is DNS server that started as a fork of [Caddy](https://github.com/mholt/caddy/). It has the
same model: it chains middleware.

## Status

Currently CoreDNS is able to:

* Serve zone data from a file, both DNSSEC (NSEC only atm) and DNS is supported.
* Retrieve zone data from primaries, i.e. act as a secondary server.
* Allow for zone transfers, i.e. act as a primary server.
* Use Etcd as a backend, i.e. a 90% replacement for
  [SkyDNS](https://github.com/skynetservices/skydns).
* Serve as a proxy to forward queries to some other (recursive) nameserver.
* Prove metrics (by using Prometheus)
* Rewrite queries (both qtype and qname).
* Provide Logging.

There are corner cases not implement and some blatantly missing functionality; i.e. the secondary
implementation *does not* requery the primary -- *ever*, leading to stale data if the server is
not restarted.

> CoreDNS is running on port 1053 on `linode.atoom.net`. This is one step from being run on port 53.
> See [this blog article](https://miek.nl/2016/April/03/running-coredns/) on this, or this
> [bug](https://github.com/miekg/coredns/issues/15) on the progress of running CoreDNS as my
> production nameserver.

But all in all, CoreDNS should already be able to provide you with enough functionality to replace
parts of BIND9, Knot, NSD or PowerDNS.

CoreDNS is still in the early stages of development and should **not** be used on production servers
yet. For now most documentation is in the source and some blog articles can be [found
here](https://miek.nl/tags/coredns/). If you do want to use CoreDNS in production, please let us
know and how we can help.

{'fraction_non_alphanumeric': 0.07717462393721386, 'fraction_numerical': 0.006540222367560497, 'mean_word_length': 4.0898502495840265, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 7, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3413390', 'n_tokens_mistral': 940, 'n_tokens_neox': 890, 'n_words': 454}