At NS1, we’ve provided two ways to get data from your application stack to our platform. This article will give a high level overview of both methods, and provide guidance on how it all works as well.
One of the unique features of the NS1 platform is the ability to take data that is important to you, and more importantly your customers and users, and make informed traffic steering decisions based on that.
Whether your aim is to replace an existing server or to bolster your infrastructure with additional resources, this article explains how using NS1’s Filter Chain can make that transition as seamless as possible.
As the notion of today’s Internet became a more pervasive thing, early attempts at redundancy resulted in some interesting experiments by curious technologists.
In the context of the DNS, delegation is the assignment of name servers to a given domain name. This information tells the respective registry where the authoritative servers live for a name, so that DNS resolution can happen.
The chief difference between a CNAME record and an ALIAS record is not in the result—both point to another DNS record—but in how they resolve the target DNS record when queried.
When managing a network, there are a number of common and uncommon DNS-specific issues that can arise.
In many cases, where a domain may not be owned by a given entity, but control over a certain part of that name is being granted, subdelegation is the answer.
The dig command is a powerful tool for troubleshooting queries and responses received from DNS - here's how to use dig+trace to understand DNS resolution from start to finish.
Request a Demo
Looking for help? Please email [email protected]