Michael Wohlmuther | 9 Jan 2007 23:38

bind dlz with postgres 8.1

hello everybody,

i am testing bind-dlz with bind version 9.2 on my university, the mysql
driver is running very good and everything is ok.

but when i try to run bind with the dlz-postgres driver (with postgresql
8.1 server at localhost) and an appropriate configuration-file i get the
following messages at the start of named:

root <at> projectbind:~# named -g -d5
Jan 09 23:37:17.457 starting BIND 9.2.2 -g -d5
Jan 09 23:37:17.458 using 1 CPU
Jan 09 23:37:17.458 Registering DLZ postgres driver.
Jan 09 23:37:17.458 Registering SDLZ driver 'postgres'
Jan 09 23:37:17.458 Registering DLZ driver 'postgres'
Jan 09 23:37:17.458 Registering DLZ mysql driver.
Jan 09 23:37:17.458 Registering SDLZ driver 'mysql'
Jan 09 23:37:17.458 Registering DLZ driver 'mysql'
Jan 09 23:37:17.458 Registering DLZ ldap driver.
Jan 09 23:37:17.458 Registering SDLZ driver 'ldap'
Jan 09 23:37:17.458 Registering DLZ driver 'ldap'
Jan 09 23:37:17.462 loading configuration from '/etc/named.conf'
Jan 09 23:37:17.462 set maximum stack size to 4294967295: success
Jan 09 23:37:17.462 set maximum data size to 4294967295: success
Jan 09 23:37:17.462 set maximum core size to 4294967295: success
Jan 09 23:37:17.463 set maximum open files to 1024: success
Jan 09 23:37:17.463 listening on IPv4 interface lo, 127.0.0.1#53
Jan 09 23:37:17.463 clientmgr  <at> 0x8175cc0: create
Jan 09 23:37:17.463 clientmgr  <at> 0x8175cc0: createclients
Jan 09 23:37:17.463 clientmgr  <at> 0x8175cc0: create new
(Continue reading)

mwohlmuther | 10 Jan 2007 10:41

Re: bind dlz with postgres 8.1

Hello!

Now I've reinstalled postgresql 8.1 with the Ubuntu (6.06.1) package 
manager.
Removed bind aka. named completely from my PC.

Then i've created a new folder and unpacked the bind-9.2.2 and dlz.

** patched with patch -p0 < dlz.path (everything was ok)
** configured with ./configure --with-dlz-postgres (everything was ok)
** make
** make install

then I've started named with "named -g -d5" ... and I got the same 
error message like before...

OUTPUT WHEN STARTING NAMED:

root <at> projectbind:~# named -g -d5
Jan 10 10:38:49.340 starting BIND 9.2.2 -g -d5
Jan 10 10:38:49.340 using 1 CPU
Jan 10 10:38:49.340 Registering DLZ postgres driver.
Jan 10 10:38:49.340 Registering SDLZ driver 'postgres'
Jan 10 10:38:49.340 Registering DLZ driver 'postgres'
Jan 10 10:38:49.347 loading configuration from '/etc/named.conf'
Jan 10 10:38:49.348 set maximum stack size to 4294967295: success
Jan 10 10:38:49.348 set maximum data size to 4294967295: success
Jan 10 10:38:49.348 set maximum core size to 4294967295: success
Jan 10 10:38:49.348 set maximum open files to 1024: success
Jan 10 10:38:49.348 listening on IPv4 interface lo, 127.0.0.1#53
(Continue reading)

Rob Butler | 10 Jan 2007 21:06
Picon
Favicon

Re: bind dlz with postgres 8.1

Can you send the dump output?

----- Original Message ----
From: "mwohlmuther <at> aim.com" <mwohlmuther <at> aim.com>
To: bind-dlz-testers <at> lists.sourceforge.net
Sent: Wednesday, January 10, 2007 4:41:04 AM
Subject: Re: [Bind-dlz-testers] bind dlz with postgres 8.1

Hello!

Now I've reinstalled postgresql 8.1 with the Ubuntu (6.06.1) package 
manager.
Removed bind aka. named completely from my PC.

Then i've created a new folder and unpacked the bind-9.2.2 and dlz.

** patched with patch -p0 < dlz.path (everything was ok)
** configured with ./configure --with-dlz-postgres (everything was ok)
** make
** make install

then I've started named with "named -g -d5" ... and I got the same 
error message like before...

OUTPUT WHEN STARTING NAMED:

root <at> projectbind:~# named -g -d5
Jan 10 10:38:49.340 starting BIND 9.2.2 -g -d5
Jan 10 10:38:49.340 using 1 CPU
Jan 10 10:38:49.340 Registering DLZ postgres driver.
(Continue reading)

Michael Wohlmuther | 10 Jan 2007 21:10

Re: bind dlz with postgres 8.1

Sorry I'm not so familiar with that, how do I get the dump output? In
which ?logfile? can I find it?

Am Mittwoch, den 10.01.2007, 12:06 -0800 schrieb Rob Butler:
> Can you send the dump output?
> 
> ----- Original Message ----
> From: "mwohlmuther <at> aim.com" <mwohlmuther <at> aim.com>
> To: bind-dlz-testers <at> lists.sourceforge.net
> Sent: Wednesday, January 10, 2007 4:41:04 AM
> Subject: Re: [Bind-dlz-testers] bind dlz with postgres 8.1
> 
> Hello!
> 
> Now I've reinstalled postgresql 8.1 with the Ubuntu (6.06.1) package 
> manager.
> Removed bind aka. named completely from my PC.
> 
> Then i've created a new folder and unpacked the bind-9.2.2 and dlz.
> 
> ** patched with patch -p0 < dlz.path (everything was ok)
> ** configured with ./configure --with-dlz-postgres (everything was ok)
> ** make
> ** make install
> 
> then I've started named with "named -g -d5" ... and I got the same 
> error message like before...
> 
> OUTPUT WHEN STARTING NAMED:
> 
(Continue reading)

Pascal Bouchareine | 12 Jan 2007 10:24
Gravatar

mysql_reconnect, REQUIRE((((zone) != 0), wildcards

Hello,

We noticed three problems with dlz that we patched more or
less efficiently. Bugs have been reported to ISC too.

//
1. mysql_reconnect - As of 5.0.3 mysql_ping does not reconnect
automatically if not asked to. Some patch attached against
dlz_mysql_driver.c

//
2. REQUIRE((((zone) != 0)...
The following error:

Jan 11 11:30:30 host named[6893]: zone.c:5919: REQUIRE((((zone)
                != ((void *)0)) && (((const isc__magic_t *)(zone))->magic
                == ((('Z') << 24 | ('O') << 16 | ('N') << 8 | ('E'))))))
                failed

Is raised when querying, for example, a non-existing RR with qtype=SOA
in a dlz zone.

We patched this the following way but i'm affraid this is not what
the code wants (a zero ttl):

                /*
                 * Add SOA.  If the query was for a SOA record force the
                 * ttl to zero so that it is possible for clients to find
                 * the containing zone of an arbitrary name with a stub
                 * resolver and not have it cached.
(Continue reading)

Stephane Bortzmeyer | 17 Jan 2007 10:07
Picon

Directive "dlz" ignored on NetBSD but not on FreeBSD?

I'm playing with BIND 9.4rc1 and I've enabled DLZ by compiling with
--with-dlz-postgres. On a FreeBSD 5.4 machine, it works fine. On a
NetBSD 3.0 box, there is no error message (configure, make, running
named, everything goes well, nothing in the named log) but I see no
connection in the PostgreSQL log and no attempt to do SQL queries.

Same named.conf for both (the sample one on
http://bind-dlz.sourceforge.net/postgresql_driver.html).

PostgreSQL is 8.1.3 in both cases. I've tested PostgreSQL and its
logging by hand on the two machines.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Rob Butler | 17 Jan 2007 14:11
Picon
Favicon

Re: Directive "dlz" ignored on NetBSD but not on FreeBSD?

Are you starting the right named?   Sometimes there is an existing Bind installation on the box and if you just
executed "named" it will start the one without DLZ.  Be sure to specify the full path to the install of Bind
that you want to start.

Rob

----- Original Message ----
From: Stephane Bortzmeyer <bortzmeyer <at> nic.fr>
To: bind-dlz-testers <at> lists.sourceforge.net
Sent: Wednesday, January 17, 2007 4:07:39 AM
Subject: [Bind-dlz-testers] Directive "dlz" ignored on NetBSD but not on FreeBSD?

I'm playing with BIND 9.4rc1 and I've enabled DLZ by compiling with
--with-dlz-postgres. On a FreeBSD 5.4 machine, it works fine. On a
NetBSD 3.0 box, there is no error message (configure, make, running
named, everything goes well, nothing in the named log) but I see no
connection in the PostgreSQL log and no attempt to do SQL queries.

Same named.conf for both (the sample one on
http://bind-dlz.sourceforge.net/postgresql_driver.html).

PostgreSQL is 8.1.3 in both cases. I've tested PostgreSQL and its
logging by hand on the two machines.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
(Continue reading)

Stephane Bortzmeyer | 17 Jan 2007 14:22
Picon

Re: Directive "dlz" ignored on NetBSD but not on FreeBSD?

On Wed, Jan 17, 2007 at 05:11:08AM -0800,
 Rob Butler <crodster2k <at> yahoo.com> wrote 
 a message of 53 lines which said:

> Are you starting the right named?

I started named by hand, giving the full path (and -c to use the
DLZ-specific named.conf). So, yes, I'm pretty confident I ran the
right one (as a test, I made a syntax error in named.conf and it
failed with the correct error message).

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Rob Butler | 17 Jan 2007 22:02
Picon
Favicon

Re: Directive "dlz" ignored on NetBSD but not on FreeBSD?

I wish I could help more but this sounds like a really weird scenario.

If you make a change to the named.conf Bind gives you an error message, so we know it is reading the named.conf
you expect.

If you had a DLZ configuration section in named.conf but didn't have the DLZ code compiled into Bind it would
give you an exception as well.  So, if there is a DLZ config section in your named.conf and it is not giving you
an error the DLZ code must have been included in the build.

So the DLZ code is in the binary, and it's in the named.conf and Bind isn't choking on the named.conf.  So it
should either connect and work fine or die with an error message when connecting to the DB, but neither are
happening for you.  hmmm..

I really don't know what else we could do to help you out.  It should either work or have an error somewhere, but
your not getting either one.  Can you double check the named.conf your using has a DLZ configuration
section?  Try performing the whole build again and see if you get better results this time.  

Sorry I couldn't do more.
Rob

----- Original Message ----
From: Stephane Bortzmeyer <bortzmeyer <at> nic.fr>
To: bind-dlz-testers <at> lists.sourceforge.net
Sent: Wednesday, January 17, 2007 8:22:51 AM
Subject: Re: [Bind-dlz-testers] Directive "dlz" ignored on NetBSD but not on FreeBSD?

On Wed, Jan 17, 2007 at 05:11:08AM -0800,
 Rob Butler <crodster2k <at> yahoo.com> wrote 
 a message of 53 lines which said:

(Continue reading)

Kreuter David | 18 Jan 2007 14:44
Picon
Favicon

ldap ipv6 problem

hallo guys,

i have installed bind-dlz driver for ldap. Everything works great! But I
have one problem. If I insert a ipv6 reverse - address into ldap, for
example:

dn:
dlzHostName=\[x0000000000000000000000000C0A80003/128],dlzZoneName=ip6.arpa,ou=dns,o=bind-dlz
objectClass: dlzHost
dlzHostName: \[x0000000000000000000000000C0A80003/128]

i get following error -> invalid dn. First i tried to escape the backslash with a second backslash or with " ->
no change. I also tried to use utf8 for the dlzHostName attribute with no improvements.

if i try to resolve a ipv6 adress with dig -x 0:0:0:0:0:0:c0a8:103  <at> localhost, i get following error
message from ldap server:

do_search: invalid dn
(dlzZoneName=\[x000000000000000000000000c0a80103/128].ip6.arpa,ou=dns,o=bind-dlz)

I hope you can help me.

best regards,

david

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
(Continue reading)


Gmane