The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) server
Go to file
2008-12-15 14:43:37 +00:00
.cvsignore - 9.6.0rc1 release 2008-12-03 12:38:21 +00:00
bind95-rh461409.patch - IDN output strings didn't honour locale settings (#461409) 2008-09-17 08:03:03 +00:00
bind-9.3.1rc1-fix_libbind_includedir.patch do not let libbind include files wipe out system headers! 2005-02-19 00:08:17 +00:00
bind-9.3.1rc1-sdb_tools-Makefile.in - improved sdb_tools Makefile.in 2008-02-12 11:40:19 +00:00
bind-9.3.2-redhat_doc.patch - 9.6.0rc1 release 2008-12-03 12:38:21 +00:00
bind-9.3.2b1-fix_sdb_ldap.patch - updated patches due new rpm (--fuzz=0 patch parameter) 2008-07-21 10:47:18 +00:00
bind-9.3.2b2-sdbsrc.patch Upgrade to 9.3.2rc1 2005-12-03 00:10:48 +00:00
bind-9.3.3rc2-rndckey.patch updated to 9.4.0 bind-chroot-admin now using restorecon instead chcon 2007-03-06 15:32:16 +00:00
bind-9.5-dlz-64bit.patch - 9.5.1b1 release (CVE-2008-1447) 2008-07-11 10:16:21 +00:00
bind-9.5-libidn2.patch - fixed shutdown with initscript when rndc doesn't work (#417431) 2007-12-11 12:23:32 +00:00
bind-9.5-libidn3.patch - fixed regression caused by libidn2 patch (#426348) 2007-12-20 13:46:29 +00:00
bind-9.5-libidn.patch - build with -D_GNU_SOURCE (#431734) 2008-02-11 17:11:26 +00:00
bind-9.5-overflow.patch handle integer overflow in isc_time_secondsastimet more gracefully 2007-07-17 06:09:36 +00:00
bind-9.5-parallel-build.patch - removed bind-9.3.2-prctl_set_dumpable.patch (upstream) 2008-01-22 16:57:44 +00:00
bind-9.5-PIE.patch - build with -D_GNU_SOURCE (#431734) 2008-02-11 17:11:26 +00:00
bind-9.5-sdb-sqlite-bld.patch - updated patches due new rpm (--fuzz=0 patch parameter) 2008-07-21 10:47:18 +00:00
bind-9.5-sdb.patch - removed conditional build with libefence (use -fmudflapth instead) 2008-02-19 10:20:49 +00:00
bind-95-rh452060.patch - 9.6.0rc1 release 2008-12-03 12:38:21 +00:00
bind-95-rh469440.patch - dig/host: use only IPv4 addresses when -4 option is specified (#469440) 2008-11-03 11:36:03 +00:00
bind-96-libtool2-libbind.patch - updates due libtool 2.2.6 2008-11-24 12:59:15 +00:00
bind-96-libtool2.patch - updates due libtool 2.2.6 2008-11-24 12:59:15 +00:00
bind-96-old-api.patch - updates due libtool 2.2.6 2008-11-24 12:59:15 +00:00
bind-96-rh475120.patch - allow to reuse address for non-random query-source ports (#475120) 2008-12-09 14:21:05 +00:00
bind-96-temporary-libbind.patch - 9.6.0b1 release 2008-11-10 16:36:47 +00:00
bind-nonexec.patch - install libbind9 correctly (and strip it) 2008-05-22 13:49:34 +00:00
bind.spec - added libxml2-devel to BuildRequires 2008-12-15 14:43:37 +00:00
Copyright.caching-nameserver - replace caching-nameserver with bind-config sub-package 2006-03-07 04:25:38 +00:00
dnszone.schema dnszone LDAP schema (http://www.venaas.no/ldap/bind-sdb/dnszone-schema.txt) 2005-02-17 17:18:07 +00:00
ldap2zone.c - updates due libtool 2.2.6 2008-11-24 12:59:15 +00:00
libbind.pc fixed some building problems 2007-01-22 13:25:36 +00:00
Makefile b* batch fix for 2007-10-15 17:09:05 +00:00
named.conf.sample - improved sample config file (#473586) 2008-12-01 16:01:44 +00:00
named.empty - major changes in initscript. Could be LSB compatible 2007-06-14 15:13:02 +00:00
named.init - 9.6.0b1 release 2008-11-10 16:36:47 +00:00
named.logrotate auto-import changelog data from bind-9.2.2.P3-9.src.rpm 2004-09-09 03:34:55 +00:00
named.sysconfig - removed statement from initscript which passes -D to named 2007-11-19 14:03:28 +00:00
README.sdb_pgsql fix bug 171226 2005-10-19 20:22:48 +00:00
rfc1912.txt auto-import changelog data from bind-9.2.1-8.src.rpm 2004-09-09 03:33:42 +00:00
sources - 9.6.0rc1 release 2008-12-03 12:38:21 +00:00

			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!