Microsoft DNS/DHCP & IPAM Challenges

Microsoft DNS/DHCP and IPAM Challenges

Microsoft Server 2008 requires Multiple Microsoft

Management Console (MMC) interfaces to manage
DNS/DHCP

No granular role based administration of DNS Records

or DHCP scopes

Administrative mistakes may require a restore from a

backup. Many times backups are not kept up to date

High availability is not built. Requires configuring a

complex Microsoft Server Clustering. DNS and DHCP
are CRITICAL network services

Microsoft Server Clusters are very difficult to setup

and maintain

No built-in network discovery capabilities

No DHCP redundancy
Split scopes create complexity

Microsoft server 2012 IP address Management is per

Active Directory forest. Companies with multiple Active
Directory forests will not have a single IPAM view

BATTLECARD | INFOBLOX CONFIDENTIAL

The Solution

How to identify opportunities

Infoblox Grid IPAM for Microsoft

The capabilities of the Infoblox Grid also

provide advantages:

Agentless architecture. No software installation

requirement. Even on Microsoft DNS and DHCP Servers

How many IP addresses do you manage?

Seamless integration with Microsoft DNS and DHCP

servers with read only and read/write capabilities

Are you using a spreadsheet to track IP addresses?

Bi-Direction management. Use the MS management tools

or Infoblox user interface. This provides a level of comfort
for both network and MS teams

Would you like better tools to assist with daily

management of MS DNS, DHCP, and IPAM to
provide more:

Centralized Administration of both Microsoft DNS and

DHCP servers and Infoblox appliances

Detailed reporting and monitoring of IP usage within

DHCP ranges including unknown devices

Split scopes create complexity

Identifies IP address conflicts

Integration with F5, Riverbed, VMware, HyperV

Network discovery (VMware, port switch, VLAN, port

speed, duplex, port description)

How many Microsoft DNS and DHCP servers are you

currently running and how are you ensuring consistency
between them?

Are you deploying a Microsoft cluster for a DHCP

redundancy?

Runs on a hardened OS

All unnecessary ports are blocked, root access is not

allowed

Secure communication among Infoblox appliances

Adds delegated access control to MS DNS and DHCP

Automation of daily DNS and DHCP changes

Security through delegated administration
Added network discovery for real time management
Central administration
Reporting on usage trends with alarms and alerts

Highly Secure:

Is the spreadsheet always up to date?

If so, have you encountered any challenges? If so,

what are they?

Have you experienced any recent failures with a

Microsoft DNS/DHCP server?

If so, how long did it take before you were able

to fully recover?

Business questions:

What is the impact to you or your company in the event

of a DNS/DHCP failure?

How many persons are involved in the management of

DNS and DHCP servers?

Do you have plans for to grow and expand your

network? If so, will your current DNS/DHCP
infrastructure be able to handle such a growth?

2013 Infoblox Inc. All Rights Reserved. June 2013 | 1