mirror of
https://github.com/isc-projects/bind9.git
synced 2026-03-18 00:26:11 -04:00
58bd26b6cf
This commit converts the license handling to adhere to the REUSE specification. It specifically: 1. Adds used licnses to LICENSES/ directory 2. Add "isc" template for adding the copyright boilerplate 3. Changes all source files to include copyright and SPDX license header, this includes all the C sources, documentation, zone files, configuration files. There are notes in the doc/dev/copyrights file on how to add correct headers to the new files. 4. Handle the rest that can't be modified via .reuse/dep5 file. The binary (or otherwise unmodifiable) files could have license places next to them in <foo>.license file, but this would lead to cluttered repository and most of the files handled in the .reuse/dep5 file are system test files.
92 lines
3.3 KiB
Text
92 lines
3.3 KiB
Text
<!--
|
|
Copyright (C) Internet Systems Consortium, Inc. ("ISC")
|
|
|
|
SPDX-License-Identifier: MPL-2.0 and ISC
|
|
|
|
This Source Code Form is subject to the terms of the Mozilla Public
|
|
License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
file, you can obtain one at https://mozilla.org/MPL/2.0/.
|
|
|
|
See the COPYRIGHT file distributed with this work for additional
|
|
information regarding copyright ownership.
|
|
|
|
Copyright (C) Red Hat
|
|
|
|
Permission to use, copy, modify, and/or distribute this software for any
|
|
purpose with or without fee is hereby granted, provided that the above
|
|
copyright notice and this permission notice appear in all copies.
|
|
|
|
THE SOFTWARE IS PROVIDED "AS IS" AND AUTHORS DISCLAIMS ALL WARRANTIES WITH
|
|
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
|
|
AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
|
|
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
|
|
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
|
|
OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
|
PERFORMANCE OF THIS SOFTWARE.
|
|
-->
|
|
|
|
To use the Dynamic DB sample driver, run named and check the log.
|
|
|
|
$ cd testing
|
|
$ named -gc named.conf
|
|
|
|
You should be able to see something like:
|
|
|
|
zone test/IN: loaded serial 0
|
|
zone arpa/IN: loaded serial 0
|
|
|
|
This means that the sample driver created empty zones "test." and
|
|
"arpa." as defined by "arg" parameters in named.conf.
|
|
|
|
$ dig @localhost test.
|
|
|
|
should work as usual and you should be able to see the dummy zone with
|
|
NS record pointing to the zone apex and A record with 127.0.0.1:
|
|
|
|
;; ANSWER SECTION:
|
|
test. 86400 IN A 127.0.0.1
|
|
test. 86400 IN NS test.
|
|
test. 86400 IN SOA test. test. 0 28800 7200 604800 86400
|
|
|
|
This driver creates two empty zones and allows query/transfer/update to
|
|
all IP addresses for demonstration purposes.
|
|
|
|
The driver wraps the RBT database implementation used natively by BIND,
|
|
and modifies the addrdataset() and substractrdataset() functions to do
|
|
additional work during dynamic updates.
|
|
|
|
A dynamic update modifies the target zone as usual. After that, the
|
|
driver detects whether the modified RR was of type A or AAAA, and if so,
|
|
attempts to appropriately generate or delete a matching PTR record in
|
|
one of the two zones managed by the driver.
|
|
|
|
E.g.:
|
|
|
|
$ nsupdate
|
|
> update add a.test. 300 IN A 192.0.2.1
|
|
> send
|
|
|
|
will add the A record
|
|
a.test. 300 IN A 192.0.2.1
|
|
|
|
and also automatically generate the PTR record
|
|
1.2.0.192.in-addr.arpa. 300 IN PTR a.test.
|
|
|
|
AXFR and RR deletion via dynamic updates should work as usual. Deletion
|
|
of a type A or AAAA record should delete the corresponding PTR record
|
|
too.
|
|
|
|
The zone is stored only in memory, and all changes will be lost on
|
|
reload/reconfig.
|
|
|
|
Hints for code readers:
|
|
- Driver initialization starts in driver.c: dyndb_init() function.
|
|
- New database implementation is registered by calling dns_db_register()
|
|
and passing a function pointer to it. This sample uses the function
|
|
create_db() to initialize the database.
|
|
- Zones are created later in instance.c: load_sample_instance_zones().
|
|
- Database entry points are in structure db.c: dns_dbmethods_t
|
|
sampledb_methods
|
|
- sampledb_methods points to an implementation of the database interface.
|
|
See the db.c: addrdataset() implementation and look at how the RBT
|
|
database instance is wrapped into an additional layer of logic.
|