Opens yourdomain.com.
Your domain's control layer: RagonsFlare DNS
Manage the DNS records that connect your website, email, and applications to the correct destination from a single panel. Securely migrate your existing zone, monitor the nameserver transition, and apply critical changes with a validation layer.
8 record types Controlled import 24/7 expert support
203.0.113.1036002001:db8::103600mail.alanadiniz.com14400v=spf1 include:…14400Manage the layer where every connection begins
When a visitor enters your domain, DNS locates the correct web server, email system, or service. RagonsFlare makes this routing map readable, portable, and auditable.
Responds with the correct record within the authoritative zone.
Web, email, API, or application responds.
Records you will need in your zone
Build your core DNS architecture—from IPv4 and IPv6 routing to business email, certificate authorization, and service discovery—through a single interface.
Connects the domain to an IPv4 address.
Connects the domain to an IPv6 address.
Points one name to another hostname.
Routes messages to the correct mail server.
Stores SPF, DKIM, DMARC, and service verifications.
Determines which organizations can issue SSL certificates.
Defines the service target, port, and priority.
Delegates DNS authority for a subdomain to other servers.
203.0.113.10TTL3600yourdomain.comTTL3600mail.alanadiniz.comTTL14400SOA and primary NS records cannot be accidentally deleted. Record content is validated based on its type and zone.
Visible, controlled, and secure changes in a single panel
View the zone status, nameserver transition, and record count on a single screen. When adding a new record, benefit from type, domain name, TTL, and content validation.
Preview existing DNS responses; transfer only the records you have validated to the new zone.
Monitor public NS responses to identify incomplete or incorrect delegations early.
IP, hostname, MX priority, SRV, and CAA values are validated according to the record type.
A zone serial check is applied to prevent records from being overwritten with stale data during concurrent operations.
Changing your DNS provider consists of four controlled steps
Leave the Nameserver change until the very end. Preparing the zone records first, especially verifying MX, SPF, DKIM, and DMARC values, reduces the risk of downtime.
- 01
Add the domain name
Connect the domain name you want to manage to the RagonsFlare service; the zone is prepared without affecting live traffic yet.
- 02
Scan records
Scan existing A, AAAA, CNAME, MX, TXT, and CAA responses; compare the records found with those from your source provider.
- 03
Validate critical values
Thoroughly verify web IPs, the www CNAME, MX, SPF, DKIM, DMARC, and verification TXT records.
- 04
Complete the nameserver delegation
Change the NS addresses at the registrar and monitor them until the delegation status in the customer panel becomes active.
Compare the right layer and do not migrate dependencies you do not need
RagonsFlare moves your domain's authoritative DNS management to the Hostragons customer panel. Cloudflare, meanwhile, is a broad edge platform that provides a reverse proxy, CDN, and WAF together with DNS. The two services overlap in DNS management, but their scopes are not identical.
DNS finds the correct destination. CDN delivers content from edge locations; reverse proxy and WAF operate in front of web traffic. The additional performance and security features included in RagonsFlare plans should be evaluated according to the scope of your chosen plan.
Making changes in the correct order is just as important as adding the correct record
DNS changes are not merely about updating an IP address. Cache duration, email verifications, certificate authorities, and nameserver delegation work in relation to one another. The approach below helps you achieve more predictable results in routine changes and infrastructure migrations.
Plan the TTL before making changes
TTL determines how long a DNS response is stored by resolvers. Lowering the TTL in a controlled manner before a server migration or IP change ensures that the old response is retained for a shorter period. After the migration is complete and the new target has been verified, you can reduce unnecessary query load by restoring the TTL to its normal level.
Check email records as a single chain
An MX record identifies the mail server; SPF defines which sources are allowed to send email, DKIM defines the message signature, and DMARC defines the policy to apply when verification fails. Migrating only the MX record is not sufficient. When changing providers, verifying these four components together reduces delivery issues and the risk of messages ending up in the spam folder.
Evaluate the root domain name and subdomains separately
While the root domain name is usually connected directly to the server with an A or AAAA record, subdomains such as www may follow another hostname via CNAME. API, control panel, store, and verification subdomains may each have a different target. Checking that each record is still in use before importing the scan results prevents forgotten connections from pointing to the old infrastructure.
Deliberately restrict certificate authority with CAA
A CAA record specifies which certificate authorities may issue certificates for your domain name. Changing the nameserver without comparing the existing CAA policy with the new certificate provider may unexpectedly halt SSL renewal. Before the migration, add to the zone the authorization required by your web server, CDN, or edge service that uses automated certificates.
Do not confuse DNS with web protocols
DNS directs the domain name to the target infrastructure, while HTTP/2, HTTP/3, and TLS 1.3 are provided by the target web server or reverse proxy. Likewise, CDN, cache, and WAF are separate layers that handle web traffic. A correct DNS record does not automatically enable these features; evaluate the scope of your chosen plan and the target system together.
Record a rollback point before making changes
Before editing a zone, save the name, type, content, priority, and TTL value of the existing records. Verify the new responses from different networks; test email, API, and third-party verifications as well as the website. Being able to view the previous values in full when an unexpected result occurs enables a quick and controlled rollback instead of guesswork-based intervention.
Four clear plans, one DNS management experience
Choose the right tier, from a personal domain name to critical enterprise applications. All plans start with the RagonsFlare panel and DNS record management; distribution, performance, and security coverage expand with the plan.
STARTER
Personal websites and new projects
Manageable DNS Content Delivery Network (CDN) Unmetered DNS queries DDoS protection Easy IP blocking DNS failover
Premium
Professional websites
Everything in the STARTER plan Domain aliases Domain forwarding DNS firewall Email forwarding Advanced DNS distribution
Business
Online businesses and stores
Everything in the Premium plan Accelerated mobile pages Lossless image optimization Network prioritization Advanced performance layer Business-focused protection
ENTERPRISE
Critical workloads and enterprise systems
Everything in the Business plan PCI DSS 3.2 compliance %99.9 uptime SLA Bot mitigation Layer-3 DDoS protection Enterprise traffic management
A security layer behind every record change
An incorrect DNS record can affect your website, email, and verification workflows at the same time. RagonsFlare focuses on detecting the most common operational errors, from zone boundaries to concurrent updates, before the record is applied.
Talk to a DNS expertPrevents records from extending beyond the zone
Record names are restricted to the domain name associated with the service; names targeting another zone are not processed.
Protects critical records
SOA and primary nameserver records are protected against accidental deletion or invalid changes.
Validates content based on its type
IPv4, IPv6, hostname, MX priority, SRV fields, and CAA values are validated according to their own rules.
Prevents overwriting with stale data
Zone serial control prevents outdated data from overwriting a new record during concurrent edits.
Provides TTL control
Manage TTL values between 60–86400 seconds; lower them before a planned migration to speed up propagation.
Makes the delegation status visible
Track public NS responses as pending or active; detect incomplete delegation early.
No matter which service your domain connects to
Website and application
Connect your website, API, or SaaS application to the right infrastructure using A, AAAA, and CNAME records.
Business email
Manage MX, SPF, DKIM, and DMARC records together to establish the foundation for deliverability and domain reputation.
Multi-cloud and migration
When you change your infrastructure provider, update only the target records in a controlled manner without transferring the domain.
Agencies and multiple domains
Monitor the zones of different projects from the same customer account while keeping the records for each domain separate.
Frequently Asked Questions
Clear answers to the most frequently asked questions about DNS hosting, Cloudflare alternatives, record migration, and plan scope.
Ready to migrate your DNS?
Start with the free plan, prepare your records without affecting live traffic, and complete the nameserver transition under your control.