Cisco DDM, Checkpoint Meta-IP, Dynamic DNS, DHCP, and Bind compatability

[Cricket Liu]

> Concern:  We currently use the patched BIND 8.2.2 release for our primary
and secondary DNS servers.  I do NOT want to migrate this to the Cisco or
Checkpoint products for a variety of reasons, most of them having to do with
security and some functionality available within the BIND release that is
not available in the other products.
>
> Question:  Can I use just the DHCP/DDNS portion of these products,
allowing these services to "securely" use DDNS to update the zone files of a
seperate instance of BIND/named?  Ultimately, I would imagine that there
will be at least 4 physically and logically seperate DHCP servers, and a
fifth Windows 2000 server handling its unique concerns.  In turn, they will
be updating four BIND DNS servers.  Or does the functionality of these two
products require complete integration?

Meta IP can manage your existing BIND 8.2.2-P5 name servers.  It uses
a service control manager to send new named.conf files over to the name
server, reload it, etc.  You don't need to replace the name server itself.
And if you did, the name server in Meta IP 4.1 SP3 is 8.2.2.-P6,
actually.

cricket

Acme Byte & Wire
cricket at acmebw.com
www.acmebw.com

Attend the next Internet Software Consortium/Acme Byte & Wire
DNS and BIND class!  See www.acmebw.com/training.htm for
the schedule and to register for upcoming classes.