Oddly, it looks like (and because it's linux, it's likely) you would be giving up secure DDNS updates if you went that route.
The organizations I've seen in the past, used similar arguments to separate DNS and DHCP to the one you posted Tom. They spent WAY more then I think they should for something freely available as a download if using *nix is expected and comes included with the Windows OS if you're using AD.
Along those lines, while AD does support having it's DNS on another solution, consider the impact to services if you add that complexity. Consider it along with the idea that most AD related issues are name resolution based. Is this type of complexity worth the impact? Maybe. But I think if it's not broken and there are no clearly defined goals, it's best to move on to more pressing and important issues within the organization.
DHCP is too basic a service to worry too much about. DNS is a foundational service that must be right and must be operational. If you start to lose this battle, do yourself a favor and at least retain the forest DNS within AD. You'll at least get to go home at night on a regular basis.
Al
On 12/19/05, AdamT <[EMAIL PROTECTED]> wrote:
On 12/19/05, Tom Kern <[EMAIL PROTECTED]> wrote:
> My company wants to use 3rd party dhcp product like Bluecat's Adonis 500 or
> 1000 instead of Windows DHCP.
>
> Is there really any compelling reason to dump or not dump Windows DHCP?
>
Personally, I would say that dumping the Win DHCP is probably a bad idea.
http://www.bluecatnetworks.com/products/adonis-appliances/adonis1000/features/
-gives a list of the features. See if there's anything in there which
compels you to buy their product.
--
AdamT
"Maidenhead is *not* in Kent"
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
