We have added Cloudflare DNS Firewall to Duplika’s primary DNS servers. Domains using our nameservers receive protection against DDoS attacks and responses from a cache distributed across Cloudflare’s network.
The improvement is included in our infrastructure. If your domain already uses Duplika’s DNS servers, you do not need to change its delegation, install a plugin or purchase Cloudflare separately.
Why protecting DNS matters to your business
Before opening a page, a browser needs to know which server to connect to. DNS finds that address from a name such as yourcompany.com. It also publishes the information needed to locate other services, including your domain’s email.
If DNS servers stop responding, visitors may struggle to reach your website even when its hosting is working correctly. For a store, company or professional, protecting this first step is part of keeping the service available.
How Cloudflare DNS Firewall works
Cloudflare sits in front of our authoritative DNS servers, which hold the domain records:
- The query reaches Cloudflare’s network. The location handling it is determined by the location of the DNS resolver making the query.
- If a valid cached answer is available, Cloudflare returns it. Many queries are resolved without travelling to our origin servers.
- If the origin needs to be queried, Cloudflare obtains the answer from Duplika. It returns the answer and temporarily stores it for future queries, according to the cache configuration.
At the same time, Cloudflare’s network mitigates DDoS attacks directed at the DNS service and reduces the load reaching our infrastructure. The official DNS Firewall documentation explains how it works.
What you gain by hosting with Duplika
- Greater resilience against DNS attacks. Malicious traffic encounters a distributed network before reaching the servers answering for your domains.
- A shorter journey for many queries. Global caching avoids repeated trips to the origin when an answer is already available. The actual improvement depends on the resolver, location and cache state.
- An additional layer of continuity. If origin DNS is interrupted, Cloudflare can continue serving cached answers, depending on the available records and configuration. This helps with resolution; your web server must also remain operational.
- Fewer tasks for you. Duplika manages this protection as part of the service. You do not need to maintain an integration or purchase it yourself.
The value lies in protecting a dependency every visitor needs, even before your page starts loading.
Which domains benefit?
This improvement benefits domains that use Duplika’s DNS servers. If you have delegated your domain to another provider, that provider continues answering its queries, even if you host the website with us.
If you are unsure which nameservers your domain uses, contact us and we will help you check. There is no need to change a working configuration to activate this improvement on our DNS servers.
How it complements other protection
DNS Firewall protects domain resolution. Cloudflare’s CDN and WAF work on other parts of the service: content delivery and requests to a web application. These are complementary layers, and this addition does not change an individual site’s Cloudflare plan.
We have also added Magic Transit for our servers in the United States and Europe, protecting network traffic directed to those servers. DNS Firewall helps visitors find your service; Magic Transit strengthens the route to the infrastructure hosting it.
We continue adding these improvements so that when you choose Duplika hosting, you benefit from infrastructure managed by our team and can spend more time on your project.