IBM NS1 Connect Managed DNS and Traffic Steering for AWS Workloads
User-Friendly, High-Performance DNS—But Setup Takes Some Learning
Intelligent Traffic Steering and API-First DNS Automation with IBM NS1 Connect
Enhances DNS Management with Flexibility and Control
AI-Powered Performance That Delivers
Easy to Use and Great for Connecting with Others
Reliable, Intelligent Traffic Management with Powerful Automation
Straightforward DNS Control and Flexible Traffic Management with NS1
Makes Getting a Lot Done Easy—Turns Beginners Into Pros
BM NS21 Makes My Work Duties Easier
Intelligent traffic control has improved DNS automation and now routes global API requests reliably
What is our primary use case?
My main use case for IBM NS1 Connect is handling DNS traffic and routing traffic. A specific example of how I use IBM NS1 Connect to route traffic is routing the API, the websites' API, and the apps from IBM Connect.
What is most valuable?
The best features IBM NS1 Connect offers are API deployment and automating DNS traffic routing, such as changing during deployment or incidents. The auto DNS traffic routing helps during deployment or incidents by providing more reliability and faster performance. In addition to these features, IBM NS1 Connect offers traffic gain, traffic steering, real-time failover, multi-CDN, performance-aware routing, and operational visibility. IBM NS1 Connect has positively impacted my organization through its intelligent traffic control layer, as it is not just a static domain name service, but an intelligent service.
What needs improvement?
I believe IBM NS1 Connect can be improved in several ways. The main concern I identified is the cost, which is higher than other solutions despite its uses. Additionally, they could improve their health check before routing traffic. Another improvement would be to automate changes through CI/CD. During deployment, the use of API to shift traffic gradually is an aspect I think they can improve. I believe they could do this gradually, such as 5%, 25%, or 50%, which would reduce the risk compared to switching everything at once.
For how long have I used the solution?
I have been using IBM NS1 Connect for a year.
What do I think about the stability of the solution?
IBM NS1 Connect is stable.
What do I think about the scalability of the solution?
For scalability, it mainly means we can handle large traffic volume, domain records, and complex global routing. It helps us to authenticate the DNS network, traffic steering, and API-driven operations.
How are customer service and support?
The customer support is the best, as they are always available.
Which solution did I use previously and why did I switch?
I have not previously used a different solution, as this is my first DNS work.
How was the initial setup?
My advice to others looking into using IBM NS1 Connect is that you can go with IBM NS1 Connect, but you should do better tutorials and practice.
What was our ROI?
I have seen a return on investment mainly in time saved, and since it is AI-based, fewer employees are needed.
Which other solutions did I evaluate?
Before choosing IBM NS1 Connect, I did not evaluate other options, as my first option was IBM.
What other advice do I have?
Regarding IBM NS1 Connect's AI capabilities, the accuracy and reliability of output involve least privileged API keys, API key rotation, secret management, and monitoring and alerting, with alerts on critical DNS changes. In terms of IBM NS1 Connect's AI capabilities, its governance and security provide good security, such as DNS control, since DNS changes can cause outages and redirect traffic incorrectly. There is clear control around who can change DNS and how changes are approved, through role-based access control, separation of duties, and auto audit logging. The least privileged API keys, test failover, regular test failovers, improved observability, and added rollback logic are fields that need improvement. I would rate IBM NS1 Connect an eight out of ten.