UltraDNS2 adds an independent global anycast edge network (UltraDNS2) alongside the existing UltraDNS platform, to provide a highly redundant active-active second provider, backed by a single vendor. UltraDNS2 delivers identical product features, billing, and reporting as UltraDNS.
There are many advantages to a second DNS network. The main benefit is to meet business continuity and disaster recovery goals for DNS resolution services to significantly reduce the risk of operational and resolution failure.
These actions must occur before they can launch the first attack, send the first beacon, and deliver the first phish before they can exploit any intrusion. Vercara focuses on discovering and mapping this adversary infrastructure and then leverages this knowledge combined with real-time communication pattern analysis to identify and prevent attacks before they happen, thus shifting to a proactive security paradigm.
At this time you must be an UltraDNS customer to use UltraDNS2.
UltraDNS2 will have a minimum of 18 points of presence located with geographic and Internet topology diversity at the forefront of location selection. POPs are distributed as follows: North America: 5, Europe: 4, Asia: 4, South America: 2, Africa: 1, Middle East: 1, and Oceania: 1.
Yes, UltraDNS2 will mitigate attacks utilizing the UltraDDoS Protect platform. UltraDDoS Protect offers 15+ Tbps of DDoS mitigation, one of the world’s largest dedicated data scrubbing networks.
Yes, the UltraDNS2 single pane of glass supports common API and reporting functionality across both networks.
if(test.isValidation()){
//Pause for 2 seconds in validation
test.pause(2000); }
else{
//Pause for 20 seconds during load test
test.pause(20000);
}
If, even after using “isValidation()” to reduce pause time, you’re still running past the two-minute limit, you will need to use the local-validation service. As with a load test, there is no time limit for script execution when using the local validator. Once you have verified the script works as expected on your local machine, upload the script and check the “Bypass Validation” option in the script editor. Finally, it’s advisable that you run a small load test to ensure the script behaves as expected.
Yes, UltraDNS2 has the option to have isolated nameservers per customer at an additional cost. This eliminates “noisy neighbor” issues and significantly reduces the risk of collateral damage due to attacks on other customers.
Users that are on your premises are automatically protected when UltraDDR is used as your organization’s recursive DNS solution. For users that are off your premises — or for hybrid scenarios in which users can be on-premises or off-premises at will, your administrators can deploy UltraDDR agents onto your users’ devices to ensure UltraDDR policy is enforced. The UltraDDR Agent is will soon be available for Windows, macOS, iOS, and Android platforms.
The most common error is the converted script expecting 3xx response codes, but seeing 200 instead. This is usually caused by ads, which were originally redirected to register a unique impression. When the converted script attempts to replay the same request, it is caught by the ad server as a duplicate, and the response is altered to prevent additional (false) ad impressions. The fix is as simple as removing the faulty requests or changing the expected response code to what was actually returned. For example:
c.get("http://example.com/ad?req=12345", 301);
Change to:
c.get("http://example.com/ad?req=12345", 200);
The second most common issue is content from third-party domains. The blacklist requests directive from the original RBU script will not be maintained in the Basic script. Our recommendation is to remove any third-party requests from the script. Here is an example of requests that would be removed:
c.get("https://connect.facebook.net/en_US/all.js", 200);
c.get(https://ssl.google-analytics.com/ga.js", 200);
All UltraDNS advanced features work seamlessly across both networks.
No, separate operational teams run each network.
Users that are on your premises are automatically protected when UltraDDR is used as your organization’s recursive DNS solution. For users that are off your premises — or for hybrid scenarios in which users can be on-premises or off-premises at will, your administrators can deploy UltraDDR agents onto your users’ devices to ensure UltraDDR policy is enforced. The UltraDDR Agent is will soon be available for Windows, macOS, iOS, and Android platforms.
The most common error is the converted script expecting 3xx response codes, but seeing 200 instead. This is usually caused by ads, which were originally redirected to register a unique impression. When the converted script attempts to replay the same request, it is caught by the ad server as a duplicate, and the response is altered to prevent additional (false) ad impressions. The fix is as simple as removing the faulty requests or changing the expected response code to what was actually returned. For example:
c.get("http://example.com/ad?req=12345", 301);
Change to:
c.get("http://example.com/ad?req=12345", 200);
The second most common issue is content from third-party domains. The blacklist requests directive from the original RBU script will not be maintained in the Basic script. Our recommendation is to remove any third-party requests from the script. Here is an example of requests that would be removed:
c.get("https://connect.facebook.net/en_US/all.js", 200);
c.get(https://ssl.google-analytics.com/ga.js", 200);
The Vercara DNS support team will provide phone, ticket, and email support to customers 24x7x365 to address any issues that customers may encounter.
No, while we have complete confidence in our quality assurance testing team, we will stage release software updates to each of the UltraDNS2 networks separately to avoid the possibility of introducing issues to both networks at once.
Yes, the May 6th issue was due to the addition of a new customer zone that introduced configurations that triggered a bug in the UltraDNS system causing degradation in the UltraDNS nameserver network. In the UltraDNS platform, most customers share common nameserver instances. In UltraDNS2, customers are placed in very small and isolated groups, significantly reducing the risk and impact of this class of “noisy neighbor” problem.
UltraDNS2 provides independence and isolation where it’s most valuable, at the DNS resolution edge. It enables a lower operating cost to customers by driving the DNS content delivered by both networks from a single control plane, API, and portal. UltraDNS2 customers receive the benefits of a second DNS provider without the effort of managing multiple control interfaces, and often incompatible advanced features.
