requirements.rst 1.65 KB
Newer Older
.. highlight:: none
.. _Requirements:

4 5 6 7 8 9

10 11 12 13 14

Knot DNS requirements are not very demanding for typical
installations, and a commodity server or a virtual solution will be
sufficient in most cases.

However, please note that there are some scenarios that will require
16 17 18
administrator's attention and a testing of exact requirements before
deploying Knot DNS to a production environment. These cases include deployment for a
large number of zones (DNS hosting), large number of records in one
19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
or more zones (TLD) or large number of requests.

CPU requirements

Knot DNS scales with processing power and also with the number of
available cores/CPUs.

There is no lower bound on the CPU requirements, but it should support
memory barriers and CAS (i586 and newer).

Memory requirements

Knot DNS implementation focuses on performance and thus can be quite
34 35
memory demanding. The rough estimate for memory requirements is
3 times the size of the zone in text format. Again this is only
an estimate and you are advised to do your own measurements before
deploying Knot DNS to production.
38 39 40 41 42 43

Also note that to ensure uninterrupted serving of the zone, Knot DNS
employs a Read-Copy-Update mechanism instead of locking and thus
requires twice the amount of memory for the duration of incoming

44 45
Operating system
46 47 48

Knot DNS itself is written in a portable way, but it depends on
several libraries. Namely userspace-rcu, which could be a constraint
Daniel Salzman's avatar
Daniel Salzman committed
when it comes to the operating system support. Knot DNS can be compiled
and run on most UNIX-like systems, such as Linux, \*BSD, and OS X.