bind9

Files

Michał Kępień 0041aeb751 Use dns_fixedname_initname() where possible

Replace dns_fixedname_init() calls followed by dns_fixedname_name()
calls with calls to dns_fixedname_initname() where it is possible
without affecting current behavior and/or performance.

This patch was mostly prepared using Coccinelle and the following
semantic patch:

    @@
    expression fixedname, name;
    @@
    -	dns_fixedname_init(&fixedname);
    	...
    -	name = dns_fixedname_name(&fixedname);
    +	name = dns_fixedname_initname(&fixedname);

The resulting set of changes was then manually reviewed to exclude false
positives and apply minor tweaks.

It is likely that more occurrences of this pattern can be refactored in
an identical way.  This commit only takes care of the low-hanging fruit.

(cherry picked from commit 4df4a8e731)

2018-04-10 13:09:24 -07:00

README.sdb_sqlite

…

sqlitedb.c

…

sqlitedb.h

…

zone2sqlite.c

Use dns_fixedname_initname() where possible

2018-04-10 13:09:24 -07:00

README.sdb_sqlite

			SQLite BIND SDB driver

The SQLite BIND SDB "driver" is intended as an alternative both to the
pgsqldb and dirdb drivers, for situations that would like the management
simplicity and convenience of single filesystem files, with the additional
capability of SQL databases.  It is also intended as an alternative to
the standard dynamic DNS update capability in bind, which effectively
requires use of DNSSEC keys for authorization and is limited to 'nsupdate'
for updates.  An sqlite database, by contrast, uses and requires only
normal filesystem permissions, and may be updated however a typical SQLite
database might be updated, e.g., via a web service with an SQLite backend.

This driver is not considered suitable for very high volume public
nameserver use, while likely useful for smaller private nameserver
applications, whether or not in a production environment.  It should
generally be suitable wherever SQLite is preferable over larger database
engines, and not suitable where SQLite is not preferable.

Usage:

o Use the named_sdb process ( put ENABLE_SDB=yes in /etc/sysconfig/named )

o Edit your named.conf to contain a database zone, eg.:
  
zone "mydomain.net." IN {
        type master;
        database "sqlite /etc/named.d/mydomain.db mydomain";
        #                ^- DB file               ^-Table
};

o Create the database zone table
  The table must contain the columns "name", "rdtype", and "rdata", and
  is expected to contain a properly constructed zone.  The program
  "zone2sqlite" creates such a table.
  
  zone2sqlite usage:
    
    zone2sqlite origin zonefile dbfile dbtable

    where
	origin   : zone origin, eg "mydomain.net."
	zonefile : master zone database file, eg. mydomain.net.zone
	dbfile   : name of SQLite database file
        dbtable  : name of table in database

---
# mydomain.net.zone:
$TTL 1H
@       SOA     localhost.      root.localhost. (       1
                                                3H
                                                1H
                                                1W
                                                1H )
        NS      localhost.
host1   A       192.168.2.1
host2   A       192.168.2.2
host3   A       192.168.2.3
host4   A       192.168.2.4
host5   A       192.168.2.5
host6   A       192.168.2.6
host7   A       192.168.2.7
---

# zone2sqlite mydomain.net. mydomain.net.zone mydomain.net.db mydomain

will create/update the 'mydomain' table in database file 'mydomain.net.db'.