The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) server
.cvsignore | ||
bind-9.2.0rc3-varrun.patch | ||
bind-9.2.2-nsl.patch | ||
bind-9.3.1-dbus_archdep_libdir.patch | ||
bind-9.3.1-next_server_on_referral.patch | ||
bind-9.3.1-redhat_doc.patch | ||
bind-9.3.1-sdb_dbus.patch | ||
bind-9.3.1beta2-openssl-suffix.patch | ||
bind-9.3.1rc1-fix_libbind_includedir.patch | ||
bind-9.3.1rc1-sdb_tools-Makefile.in | ||
bind-9.3.1rc1-sdb.patch | ||
bind-9.3.2-prctl_set_dumpable.patch | ||
bind-9.3.2-redhat_doc.patch | ||
bind-9.3.2b1-fix_sdb_ldap.patch | ||
bind-9.3.2b1-PIE.patch | ||
bind-9.3.2b2-no_servfail_stops.patch | ||
bind-9.3.2b2-sdbsrc.patch | ||
bind-9.3.3-edns.patch | ||
bind-9.3.3rc2-dbus.patch | ||
bind-9.3.3rc2-rndckey.patch | ||
bind-9.3.4-sdb-sqlite-src.patch | ||
bind-9.4.0-sdb-sqlite-bld.patch | ||
bind-bsdcompat.patch | ||
bind-chroot-admin.in | ||
bind-nonexec.patch | ||
bind.spec | ||
Copyright.caching-nameserver | ||
dnszone.schema | ||
keygen.c | ||
libbind-9.3.1rc1-fix_h_errno.patch | ||
libbind.pc | ||
localdomain.zone | ||
localhost.zone | ||
Makefile | ||
named-dbus.conf | ||
named.broadcast | ||
named.caching-nameserver.conf | ||
named.conf.sample | ||
named.init | ||
named.ip6.local | ||
named.local | ||
named.logrotate | ||
named.rfc1912.zones | ||
named.rfc1912.zones.sample | ||
named.root | ||
named.root.hints | ||
named.service | ||
named.sysconfig | ||
named.zero | ||
namedGetForwarders | ||
namedSetForwarders | ||
README.sdb_pgsql | ||
rfc1912.txt | ||
sources |
PGSQL BIND SDB driver The postgresql BIND SDB driver is of experimental status and should not be used for production systems. 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 "pgdb.net." IN { type master; database "pgsql bind pgdb localhost pguser pgpasswd"; # ^- DB name ^-Table ^-host ^-user ^-password }; 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 "zonetodb" creates such a table. zonetodb usage: zonetodb origin file dbname dbtable where origin : zone origin, eg "pgdb.net." file : master zone database file, eg. pgdb.net.db dbname : name of postgresql database dbtable: name of table in database Eg. to import this zone in the file 'pgdb.net.db' into the 'bind' database 'pgdb' table: --- #pgdb.net.db: $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 --- Issue this command as the pgsql user authorized to update the bind database: # zonetodb pgdb.net. pgdb.net.db bind pgdb will create / update the pgdb table in the 'bind' db: $ psql -dbind -c 'select * from pgdb;' name | ttl | rdtype | rdata ----------------+------+--------+----------------------------------------------------- pgdb.net | 3600 | SOA | localhost. root.localhost. 1 10800 3600 604800 3600 pgdb.net | 3600 | NS | localhost. host1.pgdb.net | 3600 | A | 192.168.2.1 host2.pgdb.net | 3600 | A | 192.168.2.2 host3.pgdb.net | 3600 | A | 192.168.2.3 host4.pgdb.net | 3600 | A | 192.168.2.4 host5.pgdb.net | 3600 | A | 192.168.2.5 host6.pgdb.net | 3600 | A | 192.168.2.6 host7.pgdb.net | 3600 | A | 192.168.2.7 (9 rows) I've tested exactly the above configuration with bind-sdb-9.3.1+ and it works OK. NOTE: If you use pgsqldb SDB, ensure the postgresql service is started before the named service . USE AT YOUR OWN RISK!