Attacks that take down your operation without warning
Botnets hiding behind CGNAT
Traffic spikes with no idea where they’re coming from
Team reacting late and by hand
Depending on the carrier to mitigate
Made4DNS is a comprehensive premium DNS stack for providers, bringing everything that used to be hidden in the CLI into a web interface.
More than just a pretty interface: it was developed by consultants who have been managing DNS for over 10 years, with each menu designed based on the most common support calls received by ISPs. Under the hood, it runs on PowerDNS + DNSdist—authoritative, recursive, secure protocols, and mitigation, all integrated.
Visibility for the customer. Operational autonomy. No CLI.
Simple settings that used to turn into a support ticket are now handled by the customer themselves in the panel. Release a network, create a zone, set up a record in seconds.
Queries per second, cache, latency, top sites, top clients. What used to be hidden in the binding is now displayed on the dashboard.
Native integration with Made4Block: automatically blocked malware signatures and lists, with a compliance report to verify compliance and avoid fines.
Automatic server-fail fallback: When a zone cannot be resolved via routing, Made4DNS redirects you and shows you exactly which sites require the attention of the networking team.
Anycast/BGP configuration via a wizard on the frontend. No need to manually edit FRR or Bird—just set the variables, and the dashboard sets everything up.
DNS in the dark poses a risk to operations.
Our DNS operation follows the security best practices of ICANN’s KINDNS initiative — DNSSEC, separation of authoritative and recursive, and secure protocols (DoT/DoH/DoQ).
From compliance to real-time visibility.
KINDNS is an ICANN initiative for DNS security best practices. Made4it adopts these practices voluntarily; this seal indicates adherence and does not constitute certification or endorsement by ICANN.
Made4DNS combines authoritative, recursive, and secure protocols into a single stack, compatible with provider environments of any size.
A complete premium DNS stack. No hidden tier restrictions.
Authoritative, recursive, secure protocols, Anatel compliance, Anycast, and specialized support from Made4it.
Save time and help your team work more efficiently
A comprehensive premium DNS stack for service providers, developed by Made4it. It combines authoritative and recursive DNS with secure protocols in a single web interface, offering real-time visibility, Anatel compliance, and Anycast—all without the need for a CLI.
No. Made4DNS was designed to be 100% frontend-operable. From zone creation to Anycast, everything is done through the control panel.
No. The panel was designed so that anyone on your team — not just the DNS specialist — can handle routine tasks: creating and adjusting zones, releasing records, monitoring traffic. Deep expertise stops being a bottleneck, and actions are logged so you can maintain governance.
Made4DNS is integrated with Made4Block, where Made4it registers security advisories and malware lists. Blocking is automatic, and you can generate a report proving compliance.
PowerDNS for authoritative/recursive DNS and DNSdist for load balancing and secure protocols — chosen for their native API integration, which enables full visibility through the dashboard.
Yes. Anycast/BGP is configured through a wizard in the frontend — you fill in the variables and Made4DNS applies them. No manually editing FRR or Bird files.
Yes: DNSSEC, DNS over TLS, DNS over HTTPS, and DNS over QUIC, with Let's Encrypt integrated for automatic certificate issuance.
KINDNS is an ICANN initiative that brings together security best practices for DNS operations. Made4DNS follows these practices — DNSSEC, separation of authoritative and recursive, and secure protocols. It is a voluntary adherence to best practices; it is not a certificate or an endorsement by ICANN.
Yes. Importing via AXFR pulls the zones from your legacy DNS directly into Made4DNS, without having to manually recreate any records.
The server-fail fallback automatically resolves the issue via public DNS and displays a list of affected domains—so you can contact the networking team only when it's truly necessary.
No. For clients that were already running Bind, the switch to the stack did not result in any significant CPU or memory overhead.
Made4it arises to meet the needs of the market, which has been demanding more and more personalized solutions.