Case study: Major financial institution
BlueCat helped a major financial institution upgrade from VitalQIP to a modern, fully supported DDI solution.
Key takeawaysThis key takeaway was generated through LLMs crawling the page and coming up with an overview of the content.A global financial institution serving over 60 million customers faced operational risk and inefficiency from a split DNS environment that used six disconnected QIP deployments for internal DNS and a separate vendor for external DNS, causing poor visibility, duplicated effort, lost data, and no automation. After Nokia ended active support for QIP and an attempted upgrade exposed database and audit-partition stability issues, the bank evaluated vendors and selected BlueCat for a unified DNS, DHCP, and IPAM platform that demonstrated superior data cleansing during QIP migration, strong automation via DNS Gateway, high availability and disaster recovery during version upgrades, and subscription-based contract flexibility. The migration to BlueCat reduced operational risk, improved data accuracy and manageability, enabled automation of standard processes, and provided a scalable purchasing model aligned with future growth.
What were the primary operational problems the financial institution experienced with its split DNS environment?
The institution’s split DNS approach produced several operational problems: lack of visibility across the enterprise meant administrators could not measure DNS performance or usage, allowing duplicative systems to persist unnoticed; inefficiency from managing DNS, DHCP, and IPAM across disconnected systems forced extra effort translating and reconciling data; gaps between systems led to lost or inaccurate data and connections over time; and the absence of an enterprise-wide platform prevented automation of routine tasks such as adding host records or managing IP addresses.
Why did the bank decide to move away from QIP and how did BlueCat address the risks associated with migration?
The bank moved away from QIP after Nokia ended active support and an attempted upgrade revealed significant operational risk due to the institution’s large database and multiple audit partitions; stability concerns during the upgrade prompted a rollback and a search for a unified platform. BlueCat addressed migration risks by running QIP migration tests that identified inaccurate or lost data other vendors missed, demonstrating data cleansing capabilities; showing high-availability and disaster-recovery functionality to enable version transitions with no downtime; and providing proven, reference-backed migration expertise specific to QIP environments.
What specific features and contract terms from BlueCat convinced the company to choose its solution?
BlueCat differentiated itself in the company’s proof-of-concept testing by providing several key advantages: data cleansing during QIP migration that surfaced inaccurate and lost records other vendors failed to capture; automation support through DNS Gateway and open-source workflows that would reduce manual effort and enable standard process automation; demonstrable high availability and disaster recovery to protect uptime during upgrades; and a subscription-style purchasing model tied to consumption rather than perpetual licensing. Together these operational and commercial factors, plus strong references from other financial services customers, led to the selection of BlueCat.
The customer
BlueCat engaged one of the world’s leading financial institutions about its DNS needs. The company serves over 60 million customers through thousands of banking and investment centers and one of the largest ATM networks in the world. The company serves clients through operations across the United States, its territories, and more than 35 countries.
The company’s network is large and complex, with active IP addresses in the millions across headquarters and field offices around the world.
The challenge
For nearly twenty years, this financial institution operated a split DNS infrastructure. Internal DNS was handled through six disconnected deployments of QIP. Another DDI vendor was used for external DNS.
This balkanized approach had several drawbacks:
- Lack of visibility: The company’s administrators were unable to measure the performance or assess usage of DNS resources across the enterprise. As a result, the duplicative effort and higher costs of running parallel systems went unchallenged for years.
- Inefficiency: Without a “single pane of glass” to manage DNS, DHCP, and IPAM resources, the company’s administrators spent undue effort translating data and deployments from system to system.
- Lost or inaccurate data: The gaps between DNS management systems allowed inaccurate data to creep in over time, resulting in lost data and connections.
- No support for automation: The lack of an enterprise-wide approach to DNS management made the automation of standard processes such as adding host records or managing IP addresses impossible.
In 2018, Nokia ended active support for its QIP product. Following that announcement, the company attempted to upgrade its QIP instances to the latest active version. This involved a great deal of operational risk due to the size of the financial institution’s database and its multiple audit partitions.
During the upgrade process, it became clear that the stability of the company’s network was at risk from continued use of QIP. The network team rolled back to a previous version and began investigating options to unify their DNS infrastructure under a single management platform.
The Solution
As part of its vendor evaluation process, the company set up proofs of concept in its internal lab environment. During this period, the company’s IT administrators and procurement staff learned about the unique benefits of BlueCat:
Data Cleansing: IT personnel ran tests of a theoretical QIP migration through the DNS management solutions provided by BlueCat and several of its top competitors. Through BlueCat’s QIP migration process, BlueCat identified a large amount of inaccurate or lost data that other vendors failed to capture.
Automation: BlueCat also demonstrated its strong support for automation through the DNS Gateway solution. Using its open source workflows for common tasks, BlueCat showed the company’s administrators how they could save time and effort while delivering greater functionality to internal stakeholders.
High Availability: Given the importance of the company to the global economy, maintaining uptime remains a clear priority. During the evaluation process, BlueCat demonstrated its disaster recovery and high availability functionality in the context of a version upgrade. Given the operational risk associated with QIP upgrades, the ability to quickly and smoothly transition to a new system version with no downtime offered clear benefits.
Contract Flexibility: The company wanted a purchasing model based on what they actually used and consumed rather than a traditional perpetual license approach. Only BlueCat was able to offer a true subscription model with parameters designed with future growth in mind.
The company chose BlueCat because it delivered the right mix of operational functionality and proven expertise in QIP migrations, delivered through flexible contract terms. The network team chose to trust BlueCat with migration of its core infrastructure based on its strong references from other financial services customers and proven record of seamless migrations from QIP.
Related content
Planning and Executing Low-Risk Migrations From Legacy DNS Platforms and Providers
Plan a DNS migration strategy that moves you off legacy DNS with minimal risk. Learn phased cutovers, data cleanup, and how to avoid self-inflicted outages.
Replacing Spreadsheet IPAM with Automated, API-Driven Address Management
From spreadsheet IPAM to automated address management. API-driven DDI workflows centralize IP data, eliminate manual work, and scale across hybrid networks.
DNS and DDI Automation for Lean NetOps and CloudOps Teams
How lean NetOps teams design DDI automation workflows that actually reduce manual DNS, DHCP, and IPAM work. Choose your path based on your constraint.
Hybrid and Multicloud Networking Strategies for Cloud Migrations
Hybrid multicloud DNS should centralize DDI, governance, and cloud integration to avoid brittle forwarding and restore visibility.