Actually it's alot easier to use MS DNS/DHCP services. It's much easier to
configure, the DNS and DHCP APIs work together, and easy to administer and
it just works. Even works together with WINS, that is if you have an
enterprise environment where they need Network Neighborhood to work across
subnets. Plus, Secure Updates work with MS DDNS/DHCP. There is no
interoperability between Unix and MS on this as of yet because the TSIGs
don't work together.
Many have chosen to use Unix. There are some tricks to get it to work, if
you want to continue to use your Unix resources. I'm just suggesting it's
way easier to use MS services for this, especially with AD.
Here's a couple links on BIND interoperablity.
Configuring Berkeley Internet Name Domain (BIND) to Support Active
Directory:
http://www.microsoft.com/technet/tr...net/prodtechnol/iis/deploy/depovg/cfgbind.asp
Support WebCast Microsoft Windows 2000 DNS and UNIX BIND DNS
Interoperability:
http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wc022602/wcblurb022602.asp
I don't have any links on 3rd party DHCP, but as long as it supports Option
081, then DDNS thru DHCP will work for client registration. Legacy client
registration will work with MS DHCP since it supports it for those clients.
I don't believe this will work with Unix' DHCP service, at least I haven't
heard, unless someone else posts otherwise. I'm also aware that MetaIP and
QIP work well too..
Here's some info on DDNS/DHCP interoperability:
Using DNS servers with DHCP:
http://www.microsoft.com/windows200...ver/help/sag_DHCP_imp_InteroperabilityDns.htm
Hope that helps out.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory