DDI Migration Preparation Services

Enterprise DDI (DNS, DHCP, IP Address Management) is an often neglected dataset that's been slowly accumulating stale, conflicting, and mistyped data over several years.

Without careful cleanup and preparation, consolidating and moving that data to a new platform is a high-risk endeavor that will negatively impact your entire organization.

A rusty industrial factory with chutes dropping boxes into overflowing containers labeled: DDI Requests

A smiling professional woman in a modern tidy and organized warehouse holding a clipboard with a satisfied expression on her face,

If you are about to migrate to or from Microsoft, Bluecat, Infoblox, VitalQIP, Diamond IP, or ISC BIND/DHCPD/Kea, you should know that data cleanup before a DDI migration is often the most expensive aspect.

Using our automation, we can significantly reduce your professional services' cost through automated DDI analysis and proven cleanup strategies. Your new system will have greatly increased accuracy, often eliminating an entire category of hard-to-reproduce network and server outages.

A typical DDI cleanup results in a greater than 25% data reduction through elimination of invalid, stale, and conflicted data.

Services

Why Migration Prep?

Deep Experience - 30 years of enterprise IT consulting, architecture planning, and software development experience, with 13 of those years focused on DDI solutions. Our tools have been used to successfully migrate hundreds of enterprise DDI customers.

Enterprise Focused - We specialize in working with Enterprise customers. We know you need change request friendly reporting, coherent descriptions of complicated problems, actionable plans, and flexibility to match your business processes.

Security is our Priority - The decades of working with finance, pharmaceuticals, defense, healthcare, and insurance ensures we utilize systems and processes that prioritize keeping your information safe and adhere to your compliance policies.

Sample DDI Issues

Sample Datasets

Issue Type

Description

Example

Impact

Recommendation

Record has invalid FQDN

Caused by incorrectly using a period terminator on a name when a relative hostname was required.

A record: server1. in zone example.org

Low - record is not resolvable

Delete record. Look for a correctly entered record that was subsequently added.

Record name contains parent zone's FQDN

Caused by forgetting to add a terminating period to a record name when entering it as a FQDN.

A record: server1.example.org.example.org.

Low - unlikely to be in use

Delete record, but be prepared to restore if a downstream device was also incorrectly configured as a workaround.

Orphaned dependent record

AD domain controller registrations for decommissioned servers.

SRV record: _ldap._tcp.dc._msdcs.example.org refers to non-existent target: oldADServer.example.org

Medium - can cause intermittent login delays for end-users.

Safe to drop after verifying that the domain controller (DC) was decommissioned. If this is for an active server, identify and remediate the cause of the failed DDNS registration from the DC.

Zone merge conflict

Conflicting data from disparate DDI systems as a result of long term de-centralized management, divestitures and or acquisitions.

zone 5.10.in-addrp.arpa is in multiple DNS sources, but has different PTRs and NS records

High - migration can't proceed until this conflict is resolved.

Identify the correct authoritative source of DNS records for this zone, then utilize NS delegation records and or forwarding to fix the recursion issue. Drop the original zone on incorrect sources.

Zone merge conflict

Conflicting targets for zone resolution

zone staging.example.com has a forwarding address: 1.2.3.4 that does not match any known delegation or load balancer in the environment.

Medium - migration shouldn't proceed until this conflict is resolved.

Identify the correct forwarding targets for the zone and update accordingly. Note: Internal firewalls or DNS ACLs may be intentionally preventing direct DNS query traffic to some servers / specific zones so verify the forwarding target IP address is consistently unresponsive from more than one subnet.

DNS recursion gap

Resolution of internal DNS zones is inconsistent, depending upon query origination.

Lame delegation records for regional sub zones in the main DNS system.

Medium - traveling users will be unable to reach compute resources in their primary region.

Identify the correct authoritative NS records for the unreachable regional subzones and update the delegation NS records in the parent zone on the main DNS system. Ensure all the updated NS FQDNs are resolvable by the main DNS recursive servers.

to of

Page of

Contact Us

Ready to work with a professional and make your job easier?

Online meeting

Schedule a free 30 minute consultation

Email

services@migrationprep.com