DDNS front-ends

[Nate Duehr]

Just a nigglet ... QIP's "standard" database that it ships with is
Sybase, but they've done so much work on their Oracle integration that
they themselves no longer recommend using Sybase, but request that you
install (or their engineers will at a very high pay rate) Oracle instead. 

At least that's the story from our rep.  Of course, they wanted so much
money for the silly thing that we realized three or four weekends with
two of us working on Perl code and we could reproduce 90% of their
entire product -- and the other stuff we didn't need anyway!  :)

Sorry if this is too OT for the bind-users list.

On Thu, Jan 04, 2001 at 01:01:45PM -0600, Scott Bertilson wrote:

> In the case of QIP, the update tools (web, GUI, CLI)
> can be configured to issue DDNS updates at the same
> time as they update the underlying Oracle database.
> This mostly works very well.  My biggest issue is that
> it is sometimes necessary to get QIP to rewrite the
> zone files from the database.  When it does this,
> there are some conditions under which the zone serial
> number doesn't get retrieved properly from "named" and
> QIP will use the last known serial number from the
> database.  This will be out of date if DDNS updates
> have taken place and slave servers will then not
> load the zone.

-- 
Nate Duehr <nate at natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.