]> git.ipfire.org Git - thirdparty/pdns.git/blame - pdns/docs/markdown/authoritative/backend-deprecated.md
remove db2 backend from build tree
[thirdparty/pdns.git] / pdns / docs / markdown / authoritative / backend-deprecated.md
CommitLineData
fc028d76
PL
1This page contains some information about deprecated backends.
2
921390f1
KM
3# DB2 Backend
4**Note**: This backend was removed in version 3.5.0.
5
6| | |
7|:--|:--|
8|Native|Yes|
9|Master|No|
10|Slave|No|
11|Superslave|No|
12|Autoserial|Yes|
13|DNSSEC|No|
14|Disabled data|No|
15|Comments|No|
16|Module name|db2
17|Launch name|db2|
18
19PowerDNS is currently ascertaining if this backend can be distributed in binary form without violating IBM DB2 licensing.
20
21## Queries
22The DB2 backend executes the following queries:
23
24### Forward Query
25select Content, TimeToLive, Priority, Type, ZoneId, 0 as ChangeDate, Name from Records where Name = ? and type = ?
26
27### Forward By Zone Query
28select Content, TimeToLive, Priority, Type, ZoneId, 0 as ChangeDate, Name from Records where Name = ? and Type = ? and ZoneId = ?
29
30### Forward Any Query
31select Content, TimeToLive, Priority, Type, ZoneId, 0 as ChangeDate, Name from Records where Name = ?
32
33### List Query
34select Content, TimeToLive, Priority, Type, ZoneId, 0 as ChangeDate, Name from Records where ZoneId = ?
35
36## Configuration Parameters
37
38### `db2-server`
39Server name to connect to. Defaults to 'powerdns'. Make sure that your nameserver is not needed to resolve an IP address needed to connect as this might lead
40
41### `db2-user`
42Username to connect as. Defaults to 'powerdns'.
43
44### `db2-password`
45Password to connect with. Defaults to 'powerdns'.
46
fc028d76
PL
47# ODBC backend
48**Note**: This backend was removed in version 3.1.
49
ff257d84 50| | |
fc028d76
PL
51|:--|:--|
52|Native|Yes|
53|Master|Yes (experimental)|
54|Slave|Yes (experimental)|
55|Superslave|No|
56|Autoserial|Yes|
57
58The ODBC backend can retrieve zone information from any source that has a ODBC driver available.
59
60**Note** This backend is only available on PowerDNS for Windows.
61
62The ODBC backend needs data in a fixed schema which is the same as the data needed by the MySQL backend. The create statement will resemble this:
63
64```
65 CREATE TABLE records (
66 id int(11) NOT NULL auto_increment,
67 domain_id int(11) default NULL,
68 name varchar(255) default NULL,
69 type varchar(10) default NULL,
70 content varchar(255) default NULL,
71 ttl int(11) default NULL,
72 prio int(11) default NULL,
73 change_date int(11) default NULL,
74 PRIMARY KEY (id),
75 KEY name_index(name),
76 KEY nametype_index(name,type),
77 KEY domainid_index(domain_id)
78 );
79```
80
81To use the ODBC backend an ODBC source has to be created, to do this see the section Installing PowerDNS on Microsoft Windows, not included in the documentation as installation on Windows is not supported.
82
83## Configuration Parameters
84### `odbc-datasource`
85Specifies the name of the data source to use.
86
87### `odbc-user`
88Specifies the username that has to be used to log into the data source.
89
90### `odbc-pass`
91Specifies the user's password.
92
93### `odbc-table`
94Specifies the name of the table containing the zone information.
95
96The ODBC backend has been tested with Microsoft Access, MySQL (via MyODBC) and Microsoft SQLServer. As the SQL statements used are very basic, it is expected to work with many ODBC drivers.
97
98# XDB Backend
99No longer part of PowerDNS.