[bind10-dev] minimum authoritative DNS server requirements ?

[Kazunori Fujiwara]

Is it a last time to say requirements?

We discussed minimum authoritative DNS server last face 2 face
meeting. The result was that minimum authoritative DNS server is
b10-auth and it runs individually.

# Currently, meeting minute is not available.
# https://bind10.isc.org/wiki/2010-09-03

I prefer minimum authoritative DNS server is one C or C++ program and
as compact as possible.

Then do we define minimum authoritative DNS server requirements ?

My idea of minimum authoritative DNS server's functions are:
- It acts as authoritative DNS server.
- It reads zone files and act as master DNS server.
- It manages slave zones (using timer/NOTIFY/AXFR/IXFR).
- It acts as master DNS server and offer zone transfer function
  (NOTIFY/AXFR/IXFR).

# NSD's function is near my idea of minimum authoritative DNS server,
# but it does not have IXFR-out function.

JPRS's case, we designed JP DNS servers hierarchically.

Zone File---Shadow Master--------------Transfer-------------Auth DNS servers
                           A/IXFR     a few servers  A/IXFR    [a-g].dns.jp
                           NOTIFY                    NOTIFY    over 30 servers

Shadow Master reads zone files and offer A/IXFR to Transfer servers.

Transfer servers receives zones from Shadow Master and 
offer zones to [a-g].dns.jp DNS servers.

Then, Transfer servers and Auth DNS servers need to have functions:
  - answering queries
  - slave zone management function using AXFR/IXFR/NOTIFY/SOA query.
  - offering zone information for slave DNS servers using AXFR/IXFR/NOTIFY.

I want to use minimum authoritative server as "Auth DNS servers" and
"Transfer servers".

-- 
Kazunori Fujiwara