We used to use both MetaIP DNS and DHCP along with a plethora of Netware server. When we migrated to Active Directory we dropped MetaIP DNS and Netware DNS and went to Microsoft AD-integrated DNS exclusively. We did keep MetaIP DHCP because of the nice-to-have features such as automatic failover to a backup DHCP server and IP address searches that Microsoft DHCP lacks.
We centralize our DNS and DHCP management to our network group who also handles all of the routers and switches for the State network. We might not compare well for your global environment since we are limited to a single state, however, our network is around 12,000 users and about 400 sites. The majority of sites are grabbing DNS and DHCP across the WAN. A few sites are getting DHCP from the local <shudder> old Netware server and a very few are getting it from a local Windows file server. As far as IP address management goes, the network group also has sole responsibility for this including assigning address ranges & subnets. I would look at using MS for DNS since it is free and if you AD-integrate your zones it is very easy to manage. Reporting is a little harder but with the "dnscmd" tool and some batch files with "FOR" statements in them, we were able to get what we need out of the DNS. I would look at MetaIP for the DHCP since the automagic failover feature is the biggest gapping hole in MS's DHCP. Our network people also can't search, report, or add MACs to Microsoft's DHCP like they can with MetaIP's. HTH, Stuart Fuller -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 07, 2004 12:22 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] Slightly OT: Enterprise IP address management? We currently have a mish-mash of Microsoft DNS and DHCP in use as well as QIP (outdated and not supported) for these services. Our network group is strongly in favor of an overall IP address management tool such as QIP or MetaIP for DNS and DHCP as these are just part of the capability of the tools. The real value to those tools lies outside of merely DHCP and DNS. They need to what device is on what address and/or whether the address is available, regardless of whether it's part of a DHCP scope or not. We also have ping blocked throughout most of the environment in response to the viruses/worms that came out some time ago. We're 65,000 users across 600 offices across 6 countries. We're currently some Active Directory and some NT4.0. We have a project to migrate to a global AD design. This effort is part of the project. What I'm hoping for is that some of you, in large environments like ours, would be kind enough to share how you're handling DNS/DHCP and IP address management so we can get some perspective. Or if you have a recommendation for a methodology or a product, please share. Our network group's biggest gripe about Microsoft DNS and DHCP is no centralized reporting or management as well as lack of support for IP addresses that lie outside of the DHCP scopes. Thanks, Mike List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
