PD == Peter van Dijk peter.van.d...@netherlabs.nl writes:
JC The ip column should not be varchar or text.
JC It should be inet.
PD We are happy to consider this change upstream
Pull request sent.
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 1024D/ED7DAEA6
signature.asc
Hello James,
On May 30, 2013, at 17:00 , James Cloos wrote:
The ip column should not be varchar or text.
It should be inet.
The proper fix is:
alter table supermasters alter COLUMN ip type inet using ip::inet;
and change the sql which creates the table during install to use inet
On Thu, May 30, 2013 at 11:00:54AM -0400, James Cloos wrote:
The proper fix is:
alter table supermasters alter COLUMN ip type inet using ip::inet;
and change the sql which creates the table during install to use inet
for that column.
Can pdns handle that table format?
As an added
tags #707761 help
thanks
On Wed, Jun 05, 2013 at 12:25:53PM +0200, Philipp Dreimann wrote:
It seems like all sql backends have weird configurations: See
https://github.com/dphi/pdns-debian/commit/80405812a940b62882537bb9859f722934b73674
for a suggestion on how to fix the inital table creation,
MH == Marc Haber mh+debian-packa...@zugschlus.de writes:
alter table supermasters alter COLUMN ip type inet using ip::inet;
and change the sql which creates the table during install to use inet
for that column.
MH Can pdns handle that table format?
It is transparent to pdns. I've been
It seems like all sql backends have weird configurations: See
https://github.com/dphi/pdns-debian/commit/80405812a940b62882537bb9859f722934b73674
for a suggestion on how to fix the inital table creation, which would
be a first step!
(I did not have a look at how updates to existing tables can be
The ip column should not be varchar or text.
It should be inet.
The proper fix is:
alter table supermasters alter COLUMN ip type inet using ip::inet;
and change the sql which creates the table during install to use inet
for that column.
That column is only supposed to hold ipv4 or ipv6
tags #707761 confirmed
Hi,
On Fri, May 10, 2013 at 10:11:01PM -0300, mar...@marcosdumay.com wrote:
The PowerDNS master/slave synchronization does not work over IPv6
because the database schema can not hold the addresses.
A supermaster can not be configured, because the column supermaster.ip
Package: pdns-backend-pgsql
Version: 3.1-4
Severity: normal
Dear Maintainer,
The PowerDNS master/slave synchronization does not work over IPv6 because the
database schema can not hold the addresses.
A supermaster can not be configured, because the column supermaster.ip holds a
maxumim of 25
9 matches
Mail list logo
