We basically use their NS1 Managed DNS service as a secondary DNS server. So essentially they front end all of the McKesson DNS queries around the world. It is a SaaS solution. So, we are using its latest version.
The biggest thing that we're doing with it is using the load balancing for CDNs. We are a sports analytics video company for coaches and athletes. We provide learning tools for them to stream their games and practices. Our video is deployed around the world in different Amazon S3 regions, and we use Fastly, CloudFront, and Quantel, depending on the region where a video is accessed. NS1 manages the DNS for our static content. It manages the DNS for our video domains, our JavaScript domains, and for any images that are streamed through our site. That's where NS1 comes into play.
Chief Technology Officer at a tech vendor with 501-1,000 employees
Real User
Feb 15, 2022
We are a marketing platform with a pretty wide range of customers around the world, from small businesses, like mom and pop shops that sell shirts, to enterprises like Salesforce or VMware, on the B2B side. Our JavaScript tags and our servers on the customer side generally have to answer requests very quickly, always be available, and not lose any data. Among our products is advertising, and that side is required to answer requests that come in from around the world. Usually they're geo-distributed when they come to us. There are many millions of requests a second that we need to handle. On the customer side, our use case is simple. Requests coming in from an end user, from their browser, need to be routed to the closest endpoint so that the latency is consistently low. The other requirement is that if one of those regions, in a very rare occurrence, is experiencing problems, we need to be able to clear traffic to a secondary or tertiary region to avoid downtime. In that situation, a little bit more latency is fine, but downtime would not be. To do this, we've always used global service load balancing, or DNS anycast, to an extent.
Director of Site Reliability Engineering at a media company with 1,001-5,000 employees
Real User
Oct 7, 2021
We use NS1 to serve our public DNS and we have around 500 domains that we service through it. It is the public resolver for our website and various other entities we own, and it has been pretty good. The solution is hosted by NS1.
Engineering Manager at a computer software company with 1,001-5,000 employees
Real User
Sep 2, 2021
We use Managed DNS, and we also partially use functionality from some of their other products such as Pulsar. We generate a DNS map and upload it to NS1 using their API to propagate to their service. Then, we use Managed DNS to find the optimal route for our users to connect to the closest point of presence for them. We use NS1 as software as a service. We are not having anything on-prem. It is a public cloud from our point of view. We are just using their cloud solution or their service. We are not installing it in our data center. They provide us with an API for us to talk to their cloud implementation.
VP Information Technology & Cyber at a computer software company with 1,001-5,000 employees
Real User
Aug 30, 2021
NS1 holds all of our domains. When we started using it, we didn't use it with API automation. Today, we do everything with automation and run everything with our automation, so that any change we run, all the data is backed up with GIT. Changes are done with an API so that there is no manual work. It reduces errors significantly and allows us to quickly roll back all the activities on the platform. It works flawlessly for us. Deployments are very fast. There's absolutely no complaint there. We manage our internet facing traffic with it.
Technical Lead - Production Engineer at a media company with 1,001-5,000 employees
Real User
Jun 24, 2021
We use NS1 as the primary point of contact, the first point of contact for a client to reach us, to discover a DNS. We use NS1 in two ways: We use the Managed DNS product and the Dedicated DNS product, which gives us redundancy. Our primary use-case is for getting users to the CDN [content delivery network] one that is best suited for each user. We have an automated deployment, so we use Terraform to deploy changes. The managed solution is completely managed by NS1; it's not on-premises.
Why
In a 24/7 world, customers demand applications, websites, and content that load instantly and are always on. When those connections are unreliable or slow, businesses don’t meet customer expectations, causing customers to leave. When that occurs, revenue may suffer.
What
IBM NS1 Connect delivers the high-performance, reliable, secure network connectivity that businesses need to meet increasingly sophisticated customer expectations. Leveraging a global network with a 100% uptime SLA,...
We basically use their NS1 Managed DNS service as a secondary DNS server. So essentially they front end all of the McKesson DNS queries around the world. It is a SaaS solution. So, we are using its latest version.
The biggest thing that we're doing with it is using the load balancing for CDNs. We are a sports analytics video company for coaches and athletes. We provide learning tools for them to stream their games and practices. Our video is deployed around the world in different Amazon S3 regions, and we use Fastly, CloudFront, and Quantel, depending on the region where a video is accessed. NS1 manages the DNS for our static content. It manages the DNS for our video domains, our JavaScript domains, and for any images that are streamed through our site. That's where NS1 comes into play.
We are a marketing platform with a pretty wide range of customers around the world, from small businesses, like mom and pop shops that sell shirts, to enterprises like Salesforce or VMware, on the B2B side. Our JavaScript tags and our servers on the customer side generally have to answer requests very quickly, always be available, and not lose any data. Among our products is advertising, and that side is required to answer requests that come in from around the world. Usually they're geo-distributed when they come to us. There are many millions of requests a second that we need to handle. On the customer side, our use case is simple. Requests coming in from an end user, from their browser, need to be routed to the closest endpoint so that the latency is consistently low. The other requirement is that if one of those regions, in a very rare occurrence, is experiencing problems, we need to be able to clear traffic to a secondary or tertiary region to avoid downtime. In that situation, a little bit more latency is fine, but downtime would not be. To do this, we've always used global service load balancing, or DNS anycast, to an extent.
We use NS1 to serve our public DNS and we have around 500 domains that we service through it. It is the public resolver for our website and various other entities we own, and it has been pretty good. The solution is hosted by NS1.
We use Managed DNS, and we also partially use functionality from some of their other products such as Pulsar. We generate a DNS map and upload it to NS1 using their API to propagate to their service. Then, we use Managed DNS to find the optimal route for our users to connect to the closest point of presence for them. We use NS1 as software as a service. We are not having anything on-prem. It is a public cloud from our point of view. We are just using their cloud solution or their service. We are not installing it in our data center. They provide us with an API for us to talk to their cloud implementation.
NS1 holds all of our domains. When we started using it, we didn't use it with API automation. Today, we do everything with automation and run everything with our automation, so that any change we run, all the data is backed up with GIT. Changes are done with an API so that there is no manual work. It reduces errors significantly and allows us to quickly roll back all the activities on the platform. It works flawlessly for us. Deployments are very fast. There's absolutely no complaint there. We manage our internet facing traffic with it.
We use NS1 as the primary point of contact, the first point of contact for a client to reach us, to discover a DNS. We use NS1 in two ways: We use the Managed DNS product and the Dedicated DNS product, which gives us redundancy. Our primary use-case is for getting users to the CDN [content delivery network] one that is best suited for each user. We have an automated deployment, so we use Terraform to deploy changes. The managed solution is completely managed by NS1; it's not on-premises.