Overview
Overview of IBM NS1 Connect Managed DNS
Learn how IBM NS1 Connect delivers the authoritative DNS that makes applications and websites resilient, with intelligent traffic steering and multi CDN optimizaton.
Overview of IBM NS1 Connect Managed DNS
What is Traffic Steering
Simplify HTTPS Management
Save 40% on annual IBM NS1 Connect subscriptions using Express Private Offer. (Renewals are excluded.)
IBM NS1 Connect is a managed authoritative DNS and traffic steering service for applications deployed across AWS, multi-cloud, and hybrid environments. The service operates on a global anycast network spanning 26 points of presence (PoPs) across 6 continents and provides a 100% uptime SLA for DNS resolution.
It integrates with AWS services including Amazon EC2, Amazon EKS, Elastic Load Balancing (ALB/NLB), Amazon CloudFront, AWS Global Accelerator and Amazon CloudWatch.
NS1 Connect enables DNS-based traffic routing using real-time data such as Real user Metrics (RUM), third party QoE data, CloudWatch metrics, health checks, latency, geographic location, and application performance signals.
The platform supports primary and secondary DNS configurations across AWS, other cloud providers, and on-premises infrastructure.
Key Capabilities
Available and Adaptable
- Global anycast DNS network with 26 PoPs across 6 continents for distributed query handling - 100% uptime SLA for DNS resolution.
- Traffic steering using real-time metrics, health checks, latency, and RUM data.
- Multi-cloud and multi-CDN routing across AWS, other cloud providers, and on-prem environments.
Agile and Secure
- API-First integration with infrstructure-as-a-service (Kubernetes, Ansible, Piulimi) Kubernetes ExternalDNS, AWS services.
- Observability integrations including Amazon CloudWatch, Datadog, Splunk, AppDynamics, Catchpoint, ThousandEyes, Pingdom.
- Security features including DNSSEC, TSIG, IP allow-listing, RBAC, SAML/SSO, AWS IAM read-only integration.
- ISO/IEC 27001 certification. SOC 2 Type II available via AWS Vendor Insights.
Frequently Asked Questions
How does NS1 Connect integrate with Amazon Route 53?
AWS and IBM offer two complementary architecture patterns that help customers expand their use of Amazon Route 53 while meeting advanced performance and resiliency requirements. With IBM Cloud Sync (an optional add-on), zones, records, traffic-steering metadata, and health checks synchronize bidirectionally between NS1 Connect and Route 53 without DNS zone-transfer (XFR). Cloud Sync also backs up NS1 Connect DNS configurations to a customer-owned Amazon S3 bucket for fast restore.
Which AWS services are used for traffic steering decisions?
NS1 Connect ingests Amazon CloudWatch metrics directly into Filter Chains, so DNS answers reflect the live health and performance of Amazon EKS, EC2, ELB, CloudFront, and other AWS resources. In addition, the Filter Chain engine ingests telemetry from third-party observability and RUM providers (Datadog, Catchpoint, ThousandEyes, AppDynamics), enabling consistent multi-cloud and multi-provider decisioning. Cloud Sync backs up NS1 Connect DNS configurations to a customer-owned Amazon S3 bucket.
What scale does the service support?
Service tiers support query volumes from tens of millions per month to custom volumes at higher scales. NS1 Essentials handles 30-80M queries/month; NS1 Standard handles 50M-1B queries/month; NS1 Premium is custom-priced and scales beyond 1B/month.
Can NS1 Connect be used as primary or secondary DNS?
Yes. It can function as either a primary authoritative DNS provider or as a secondary provider.
What security features are included?
The platform is ISO 27001 certificatied with SOC 2 Type II available on request. It supports DNSSEC, TSIG, IP allow-listing, RBAC, SAML/SSO authentication and AWS IAM integration.
Does NS1 Connect support multi-CDN routing?
Yes. It can route traffic across Amazon CloudFront and third-party CDNs based on performance using real-time RUM, CloudWatch, Catchpoint and ThousandEyes signals, including cost-aware and contract-aware shaping.
Does NS1 support multi-cloud and hybrid environments?
Yes. Traffic routing policies can be applied across AWS, other public clouds, and on-premises infrastructure. Customers commonly run NS1 Connect as the global DNS decisioning layer in front of workloads spanning multiple providers, with per-zone or per-record steering policies. Where Amazon Route 53 is also in use, IBM Cloud Sync (optional add-on) keeps zones, records, and steering metadata aligned bidirectionally without DNS zone-transfer (XFR).
How does it fit DevOps workflows?
NS1 Connect provides API access and integrates with Terraform, Ansible, Pulumi, and Kubernetes ExternalDNS integration for automatic DNS record management; webhooks and APIs for CI/CD pipelines.
Is a free trial available?
Yes. A 30-day free trial is available through AWS Marketplace.
Highlights
- Global anycast network: Primary and secondary DNS built with a fully redundant architecture at 26 locations to meet a 100% uptime SLA.
- Real-time DNS traffic steering using Real User Metrics (RUM), Amazon CloudWatch metrics, third party QoE data, latency, and health checks.
- DevOps ready integrations with EC2, EKS, ALB/NLB, CloudFront, Terraform, Ansible, Pulumi, Global Accelerator, Datadog, Splunk, ThousandEyes.
Get personalized pricing in minutes - New
Details
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Description | Cost/12 months |
|---|---|---|
Essentials | Includes 30M queries 1000 records 1 Filter Chain 2 Monitors | $1,188.00 |
Essentials with Route 53 DNS syncronization | Includes 50M queries per month, 1000 records, 1 Traffic Steering Filter Chain, 2 Monitors, 1 Cloud Sync Connection | $3,288.00 |
Essentials Large Bundle | Includes 80M queries 1000 records 1 Filter Chain 2 Monitors | $4,188.00 |
Standard-50 | 50M Queries, 1000 Records, 1 Traffic Steering Filter Chains, 2 Monitors, 50 HTTPS Redirects, Spike Protection, Zone Backup/Restore | $4,188.00 |
Standard-150 | 150M Queries, 1000 Records, 3 Traffic Steering Filter Chains, 7 Monitors, 50 HTTPS Redirects, Spike Protection, Zone Backup/Restore | $9,426.00 |
Standard-250 with Route 53 DNS syncronization | Includes 250M Queries per month, 2000 Records, 25 Traffic Steering Filter Chains, 25 Monitors, 50 HTTPS Redirects, Spike Protection, Zone Backup/Restore, 1 Cloud Sync Connection | $22,006.80 |
Standard-500 | 500M Queries, 5000 Records, 50 Traffic Steering Filter Chains, 50 Monitors, 50 HTTPS Redirects, Spike Protection, Zone Backup/Restore | $31,096.80 |
Standard-1000 | 1Bn Queries, 10000 Records, 100 Traffic Steering Filter Chains, 100 Monitors, 50 HTTPS Redirects, Spike Protection, Zone Backup/Restore | $46,546.80 |
Standard-1000 with Route 53 DNS syncronization | Includes 1Bn Queries per month, 10000 Records, 100 Traffic Steering Filter Chains, 100 Monitors, 50 HTTPS Redirects, Spike Protection, Zone Backup/Restore, 1 Cloud Sync Connection | $47,446.80 |
The following dimensions are not included in the contract terms, which will be charged based on your usage.
Dimension | Description | Cost/unit |
|---|---|---|
Overage Rate Total Queries (Requests) | Overage Rate Total Queries (Requests) | $50.00 |
Overage Rate DNS Records | Overage Rate DNS Records | $75.00 |
Overage Rate Filter Chains (Resource Units) | Overage Rate Filter Chains (Resource Units) | $103.50 |
Overage Rate Monitors (Jobs) | Overage Rate Monitors (Jobs) | $3.45 |
Overage Rate China Requests | Overage Rate China Requests | $172.00 |
Steering Standard Interaction Overage | Steering Standard Interaction Overage | $20.39 |
GSLB Standard Interaction Overage | GSLB Standard Interaction Overage | $20.39 |
Steering Advanced Interaction Overage | Steering Advanced Interaction Overage | $32.39 |
GSLB Advanced Interaction Overage | GSLB Advanced Interaction Overage | $32.39 |
Enterprise Request Overage | Enterprise Request Overage | $8.27 |
Vendor refund policy
All orders are non-cancellable and all fees and other amounts that you pay are non-refundable.
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
Self Service on All tiers including Free Trial
Connect with your peers at IBM NS1 Connect Community. https://ibm.biz/Bdbz3K Review our comprehensive IBM NS1 Connect Documentation. https://ibm.biz/Bdbz3b
IBM Customer Support Engineer: Essentials, Standard and Premium Tiers
If you have IBM Advanced Support, you receive prioritized case handling and shorter response times. https://ibm.biz/Bdbz3J
Click below to open a case to submit a request for help from an experienced Customer Support Engineer.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.


Standard contract
Customer reviews
Intelligent traffic management has improved uptime and kept latency consistently low
What is our primary use case?
In a network with significant traffic, I use IBM NS1 Connect to manage traffic in real time in an intelligent way based on the connected host in order to improve network performance.
In a network with many hosts and irregular traffic, I need a tool that guarantees low latency and high availability. IBM NS1 Connect provides a scalable DNS server that manages traffic depending heavily on time by adding or changing DNS records in real time.
IBM NS1 Connect has helped me manage the network effectively.
How has it helped my organization?
IBM NS1 Connect has had a positive impact on my organization by improving reliability and performance, which were the two main goals I obtained in the project with this product.
Regarding how reliability and performance improved, I noticed that the percentage of uptime was the first goal, achieving 99%, with the second goal being a very low TTL, measuring a time of less than five seconds.
What is most valuable?
The best feature of IBM NS1 Connect is the dynamic management of latency without fixed rules.
In testing, I have manual adjustment capabilities, but after this manual adjustment, IBM NS1 Connect can manage itself and try to scale automatically, helping me reach my goals of 99% uptime instead of experiencing problems reaching the network.
Another unique feature of IBM NS1 Connect is that it works seamlessly with both physical networks and the cloud together, ensuring effective performance for internal and cloud networks simultaneously.
Regarding IBM NS1 Connect's AI capabilities for security, I know that the product conforms to my normative requirements, and I rate it highly because it allows me to configure a dedicated, separated DNS and a secondary DNS with another provider, preventing a single point of failure, which is one of the best advantages of this product.
In terms of IBM NS1 Connect's accuracy and reliability of output, I find that it consistently chooses the best DNS, and I have not encountered any issues with accuracy in my project.
What needs improvement?
I have tried Pulsar, which is a module of IBM NS1 Connect that allows for routing traffic based on real user monitoring by collecting data from JavaScript to analyze it effectively. When a user accesses the domain, IBM NS1 Connect automatically directs them to the endpoint with the best performance.
In my project, I use only Pulsar.
For how long have I used the solution?
I have used IBM NS1 Connect for one year, which was several years ago.
What do I think about the stability of the solution?
IBM NS1 Connect is very stable.
What do I think about the scalability of the solution?
IBM NS1 Connect's scalability is very high, managing scenarios with a large volume of queries by distributing load among free nodes, and it also offers a linear cost structure relative to traffic.
How are customer service and support?
Customer support for IBM NS1 Connect is very good, with a wealth of documentation available on the IBM portal, and the IBM technical and commercial manager is very helpful when working with me.
I rate the customer support a 10 out of 10.
What was our ROI?
The main advantage for my customer using IBM NS1 Connect is its reliability, as I had high downtime before its implementation and now achieve 99% uptime, a significant improvement for my customer.
What's my experience with pricing, setup cost, and licensing?
My experience with IBM pricing, setup cost, and licensing is that I work with IBM and have a very high number of products from them. The licensing is clear on the IBM internet site, with different plans depending on traffic quantity, and some module prices are available on request. The essentials plan is very affordable, costing less than 100 a month.
Which other solutions did I evaluate?
Before implementing IBM NS1 Connect, I did not evaluate other options because my customer already had this product, so I used, configured, and tested IBM NS1 Connect without a software selection process.
What other advice do I have?
I rate IBM NS1 Connect a perfect 10 out of 10.
I choose 10 out of 10 because it stands out exceedingly well for me.
My advice for those considering IBM NS1 Connect is to purchase the Pulsar module for scalability, especially when operating in a multi-cloud environment.
Easy-to-Manage Enterprise DNS with a Powerful API
Easy DNS & SSO Integration with Seamless Multi-Instance Migrations
Centralized DNS control has improved traffic routing and maintains reliable cloud availability
What is our primary use case?
My main use case for IBM NS1 Connect is for DNS management, traffic routing, and improving application availability. In day-to-day operations, it helps us manage DNS records, route traffic efficiently, and maintain reliable connectivity for our cloud-hosted applications.
A specific example of how I use IBM NS1 Connect for traffic routing and improving application availability is managing DNS routing for a cloud-hosted application and directing users to the appropriate endpoints. When maintaining application infrastructure behind an AWS load balancer, DNS routing helps direct traffic to the configured endpoint and supports application availability during infrastructure changes.
We primarily focus on DNS management, efficient traffic routing, and maintaining reliable access to our cloud-hosted application. We also value the centralized DNS control and the ability to support availability as our infrastructure grows.
How has it helped my organization?
IBM NS1 Connect has positively impacted our organization by simplifying DNS management, improving traffic routing, and supporting the availability of our cloud-hosted application. Its automation capabilities reduce manual DNS changes and make infrastructure updates easier to manage. Overall, it helps us maintain more consistent traffic management as our cloud environment grows.
We have noticed smoother DNS management and fewer manual interventions when making infrastructure changes. API-driven automation helps simplify DNS updates and reduce the risk of configuration errors. The main benefits have been improved operational consistency and easier traffic management.
What is most valuable?
IBM NS1 Connect offers intelligent traffic routing, DNS automation, real-time traffic steering, and health-based routing. These capabilities help direct users to appropriate endpoints, improve application availability, and simplify DNS management. I also value its API-driven automation, which makes it easier to integrate DNS changes into cloud and DevOps workflows.
I find myself relying most on health-based routing because it helps direct users to healthy application endpoints and reduces the risk of sending traffic to unavailable services. Combined with an AWS load balancer, it supports application availability during infrastructure changes and helps provide a more reliable user experience.
I value IBM NS1 Connect's flexible DNS management, intelligent traffic routing, and API-driven automation. These features help simplify infrastructure operations and support application availability. Deeper monitoring insights and easier troubleshooting would make the experience even better.
What needs improvement?
IBM NS1 Connect could be improved with more intuitive dashboards, clearer troubleshooting guidance, and more detailed real-time visibility into DNS performance and traffic routing. Deeper integration with AWS monitoring tools and simpler configuration of health checks would also help teams identify issues faster and automate DNS management more efficiently.
Better documentation with practical examples, easier API integrations, and more detailed audit logs would make IBM NS1 Connect even more useful. I would also appreciate proactive alerts for DNS configuration issues, simpler setup for advanced routing policies, and clearer usage and pricing insights to help optimize performance and cost.
For how long have I used the solution?
I have been using IBM NS1 Connect for approximately four to six months.
What other advice do I have?
I would rate IBM NS1 Connect eight out of ten.
I chose eight out of ten because IBM NS1 Connect provides flexible DNS management, intelligent traffic routing, and API-driven automation that help improve application availability. However, better troubleshooting tools, more dashboards, and clearer pricing would make the overall experience even better.
Regarding IBM NS1 Connect's AI capabilities, I believe AI governance and security should prioritize data privacy, transparency, access control, and auditability. Any AI-driven recommendations in IBM NS1 Connect should be explainable, follow least-privilege principles, and allow human oversight for critical DNS and traffic routing changes. Clear documentation of how AI uses operational data would further build confidence.
AI-driven insights can be useful for identifying traffic patterns and supporting DNS troubleshooting, but their accuracy depends on the quality of the underlying data and the context. I would validate important recommendations against monitoring data before making production changes. Clearer explanations, consistent results, and human oversight are important for maintaining reliability.
We deploy IBM NS1 Connect in a public cloud environment alongside our AWS-hosted infrastructure. It supports DNS management and traffic routing for our cloud-hosted application, helping us maintain reliable connectivity and manage DNS changes efficiently.
I recommend starting with a proof of concept to test DNS management, traffic routing, and health-based routing with your existing cloud infrastructure. Evaluate its AWS integration, API automation, monitoring capabilities, and pricing before a full rollout. Configure health checks carefully and establish monitoring and rollback procedures to maintain application availability during DNS changes.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Intelligent traffic steering has improved uptime and now needs simpler policies and support
What is our primary use case?
My primary use case for IBM NS1 Connect is improving the availability and the response time for our internet-facing applications by directing users to healthy and appropriate endpoints. For example, organizations with application instances in multiple regions can use health checks and traffic steering policies to avoid sending new DNS responses to an unhealthy endpoint.
With respect to how I use health checks and traffic steering policies in my day-to-day work, it helps us improve application availability and reduce latency. For example, if the application is running in two different regions and one region becomes unhealthy or starts responding slowly, IBM NS1 Connect helps us detect the endpoint issues. A heartbeat request is sent to both servers, and if any of the servers does not acknowledge the request, then IBM NS1 Connect will assume that this server has gone down. With this, we can redirect new requests to the healthy alternative server, which reduces the need for manual DNS changes during incidents, helping us to minimize disruption for users.
How has it helped my organization?
IBM NS1 Connect impacts my organization positively by saving eight engineer hours per month; at a fully loaded cost of $40 per hour, that is $320 monthly or $3,840 annually in labor value. This avoids downtime during important incidents that require our support.
Regarding specific incidents where IBM NS1 Connect helped avoid downtime or saved significant time or money, one example is that we found routing users to a geographically nearest location did not always provide the fastest connection. We used performance-based DNS routing with IBM NS1 Connect, which reported a 10 to 15 percent latency improvement, allowing users at the 75th percentile to reach good responses while we could direct them to the nearest geographically located server. Additionally, we had a complex traffic steering situation that saved millions.
What is most valuable?
The best features IBM NS1 Connect offers include the authoritative DNS filter chain, traffic steering policies, and endpoint health monitoring, along with its API-first automation and DNS reporting, which are all some of the most valuable features.
Out of those features, I find myself relying on the traffic steering policies the most because we detect the endpoints and steer new DNS responses towards healthy alternatives. This is very helpful because whenever there is a massive amount of requests coming into the region or to the server, and for a better user interface and customer experience, we should not show the user that the server is down. We can reroute the request to the server nearest to that region, making it an important capability. The authoritative DNS ensures DNS queries for domains and reliable DNS resolution are essential for users, particularly to discover application endpoints, but it alone does not guarantee this. The API-first automation automates DNS configurations and changes through APIs and infrastructure as code workflows, reducing repetitive manual work and the risk of human error. The DNS reporting and analytics help teams understand query volume, traffic distribution, and unusual behavior under the support of troubleshooting and capacity planning.
What needs improvement?
I believe that while every service provided by IBM NS1 Connect is crucial for the future, there are areas for improvement such as making filter chain configuration easier, improving monitoring and incident troubleshooting, and possibly enhancing documentation and onboarding facilities.
Concerning the needed improvements, with regard to filter chain configuration, I think advanced traffic policies can be difficult for new teams. A visual policy builder or plain language explanations, or a simulator that shows which endpoint each rule selects, would be very helpful for new team members and would significantly reduce configuration mistakes while speeding up onboarding.
For how long have I used the solution?
My experience with IBM NS1 Connect spans one and a half years, during which I have used it in production and pilot environments. I have worked with some of the main important features.
What do I think about the stability of the solution?
IBM NS1 Connect is stable so far, and we have not faced any issues yet.
What do I think about the scalability of the solution?
The scalability of IBM NS1 Connect depends on the plan, including query record limits, monitor limits, and filter limits, but generally, the application is scalable along with the DNS traffic profile.
How are customer service and support?
Our experience with customer support has been mixed; while some team members are really helpful and responsive, there have been instances where responses to complex technical issues are slower because they need to evaluate and provide support. Moreover, I believe subscribing to a higher plan would ensure immediate support to prevent losing too many customers, particularly premium customers.
I would rate customer support as three out of ten.
Which solution did I use previously and why did I switch?
Previously, we have been using IBM Management Connect since the very beginning.
What was our ROI?
Regarding return on investment, this automation saves eight engineer hours per month, which at $40 per hour translates to about $320 monthly and approximately $3,840 annually, allowing us to save around four to five lakhs of rupees.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing reveals that before selecting this product, these factors were crucial because every organization considers these aspects before making a purchase decision. My experience indicates that the initial technical setup is fairly straightforward, and once DNS architecture and requirements are clear, the advanced graphic tools and integrations require some planning and testing. Licensing poses a more challenging part since the cost depends on the plan, DNS query volume, check monitors, filter limits, and additional capabilities. Some of our clients have described the pricing as expensive compared to alternatives, so I recommend organizations assess their requirements and desired features to better understand the implementation and costs involved.
Which other solutions did I evaluate?
Before choosing IBM NS1 Connect, we evaluated other options, specifically Amazon Route 53 and Cloudflare. We found that since Azure DNS fits naturally into our Azure ecosystem, we wanted better and optimized DNS performance and intelligent traffic steering mechanisms, leading us to choose IBM NS1 Connect based on these two standout requirements.
What other advice do I have?
I rate IBM NS1 Connect as seven out of ten.
I choose seven out of ten for IBM NS1 Connect because it provides many good definitions and capabilities such as strong intelligent traffic steering, monitoring, DNS automation, and global management. These capabilities help reduce downtime, improve application performance, and minimize manual operational work, but I find the advanced filter chain configurations present a learning curve, and troubleshooting and testing could be more intuitive. Pricing is also a concern when compared to alternatives like Amazon Route 53 and Azure DNS. Overall, it is a capable solution for our organization.
Regarding IBM NS1 Connect's governance and security capabilities, I think they are strong. Organizations are very keen to understand how their data is protected and how customer data is not breached in online security protocols, making this a crucial criterion before purchasing. I believe that IBM NS1 Connect has a solid foundation for DNS governance and security, supporting role-based user and API key management and accountability visibility. DNS security protects the integrity of DNS responses, while from a governance perspective, utility teams can manage access according to responsibilities and automate DNS changes through APIs. However, more intuitive audit and rollback capabilities directly in the interface, along with clearer visibility into changes made, are necessary. The overall security capabilities are valuable, but strong access controls, change reviews, and monitoring are still necessary to maintain a secure direction.
For IBM NS1 Connect's accuracy and reliability of output, since we have been using it, I feel it is very reliable in terms of DNS resolution and intelligent traffic steering. Its ability is phenomenal, especially when configured with accurate health checks and performance data. It helps direct users toward suitable endpoints and improve routing decisions. The output is also accurate as monitoring data checks configurations and policies to provide actual output. However, false positives, false signals, or incorrect rules can result in traffic being directed toward unsuitable endpoints, which is why I rate it as a seven. It is beneficial, but there is room for improvement.
My advice to others looking into using IBM NS1 Connect is to first figure out what their requirements are and ensure they have a clear understanding of it. For those particularly interested in optimized versions of intelligent traffic steering and health monitoring checkups, they can proceed with selecting IBM NS1 Connect, but I strongly recommend exploring other options as well.