Building Your Portfolio Experience
Loading Tariqul Islam's projects...
Loading Tariqul Islam's projects...
This guide will help you move your domain's DNS from Hostinger to Cloudflare, configure optimal SSL/TLS and performance settings, and ensure compatibility with modern applications.
Feature | Cloudflare DNS | Hostinger DNS |
|---|---|---|
Free SSL | ✅ Yes (Universal SSL) | ❌ No (manual setup) |
DDOS Protection | ✅ Built-in | ❌ None |
CDN / Global Cache | ✅ Enabled | ❌ Not available |
IP Masking / Firewall | ✅ Available | ❌ No |
Auto Performance Optimization | ✅ Brotli, Minify | ❌ Basic only |
DNS Propagation Speed | 🚀 Fast | 🐢 Slower |
Analytics and Rate Limiting | ✅ Advanced | ❌ Limited |
Best for SEO and Production | ✅ Highly Recommended | ❌ Not optimal |
Recommendation: Always use Cloudflare DNS for production websites. It’s faster, more secure, and more reliable.
Visit: https://dash.cloudflare.com
Sign up using your Gmail or email account
Click "+ Add a Site"
Enter your domain (e.g. your-domain.com)
Choose the Free Plan
Cloudflare will attempt to auto-import records from Hostinger. If not, add manually:
Type | Name | Value |
|---|---|---|
A | @ | VPS IPv4 |
A | www | VPS IPv4 |
AAAA | @ | VPS IPv6 |
AAAA | www | VPS IPv6 |
Make sure the Proxy status (orange cloud) is ON to enable Cloudflare protection.
Cloudflare will provide nameservers like:
josh.ns.cloudflare.com
lola.ns.cloudflare.comLogin to Hostinger
Go to Domains > DNS / Nameservers
Select Custom Nameservers
Paste Cloudflare's nameservers
Save and wait for propagation (usually 15 minutes to 12 hours)
Check propagation using https://dnschecker.org
If your domain was using Hostinger’s default nameservers:
ns1.dns-parking.com
ns2.dns-parking.comMake sure to remove these from your Hostinger domain panel and only use the nameservers provided by Cloudflare.
Go to SSL/TLS > Overview:
SSL Mode: Full (strict)
Always Use HTTPS: Enabled
Automatic HTTPS Rewrites: Enabled
TLS 1.3: Enabled
Minimum TLS Version: 1.2
Note: If you're using Full (strict), your VPS must have Let's Encrypt or a valid SSL certificate installed.
Navigate to Speed > Optimization:
Option | Status |
|---|---|
Auto Minify (HTML/CSS/JS) | On |
Brotli Compression | On |
Rocket Loader (JS Boost) | Optional |
Early Hints | Enabled |
Enhanced HTTP/2 Prioritization | On |
Go to Caching > Configuration:
Browser Cache TTL: 1 hour or 4 hours
Always Online: Enabled
Do not enable "Cache Everything" if your application uses SSR or ISR
Important for Next.js users: SSR/ISR depends on dynamic rendering. Avoid full-page caching to preserve reactivity.
Cloudflare > Security > Settings:
DDoS Protection: Enabled
Bot Fight Mode: Enabled
IP Access Rules: Optional for geo-blocking
Use the terminal:
dig yourdomain.comThe IP in the response should match a Cloudflare IP (e.g. 104.21.x.x), confirming that proxy is active.
Compatible with App Router, SSG, SSR, and API routes
Full (strict) SSL mode requires active SSL on your server
Do not use "Cache Everything" page rules in Cloudflare if using dynamic rendering
Cloudflare acts as a CDN, DDoS filter, and TLS endpoint. Your backend handles rendering
Your domain is now:
Accelerated with global CDN
Protected by HTTPS and Cloudflare DDoS tools
Optimized for performance and modern web app frameworks
You are ready to deploy confidently using Cloudflare and Next.js together.