We’ve always given our customers a lot of options for shaping traffic and shipping users to different datacenter facilities, CDNs, or other endpoints.
We know you’re big on saving time and making DNS configurations faster and easier. That’s why our intelligent DNS solutions let you clone records instead of creating each one individually.
NS1’s platform is fully edns0-client-subnet (ECS) enabled. This means Google Public DNS, and other ECS-enabled resolvers will send details about the user doing a DNS query, which is then used to improve routing by leveraging your NS1 Filter Chains.
DNS is the entry point into our customers’ applications, and security of your DNS records is a critical component of the security of your overall application.
The standard redundant DNS setup is to configure a Primary and Secondary provider for your DNS in a master/slave configuration. In this scenario we’ll show NS1 as the primary(master) DNS provider and another DNS provider as the secondary(slave).
We’re excited to announce that you can now leverage Catchpoint, the powerful monitoring service, as a data source feeding NSONE’s traffic management platform.
Nope, you’re not hallucinating. We went live with our new website this past weekend and are super excited to share it with you!
NSONE’s revolutionary Filter Chain technology perfectly balances the often competing interests of power, flexibility, and usability.
Third-party Data Feeds are and always will be a fundamental part of the NSONE platform.
ALIAS records are the answer to that quirky DNS problem of not being able to reliably CNAME your “naked” domain (a.k.a. “zone apex” a.k.a. “root domain”).
We love real-time data. It quickly confirms that traffic is flowing and gives a snapshot of current traffic levels. In fact, when you login to our customer portal, one of the first things you’ll see is your current queries per second (QPS)
Apache Cloudstack is an open source cloud platform that we here at NSONE know well.
Last week, we presented at AdTech Gets Hacked in Lower Manhattan over at Stack Exchange.
Planning to shift from your legacy single-datacenter application deployment to a multi-datacenter solution? Our CEO talks about how to make that happen.
APIs are great, and here at NSONE we follow a strict API-first strategy.
One of the most common DNS configurations you might want to implement is active-passive failover.