MX Record TTL Mismatch Between Cloudflare and Hostinger: Technical Impact, Behavior, and Resolution

This article explains why Cloudflare DNS does not provide a 14400-second (4-hour) TTL option while Hostinger recommends TTL 14400 for MX records, and whether this mismatch causes email delivery, DNS, or compliance issues.

It covers:

• DNS TTL behavior in Cloudflare

• Hostinger MX record expectations

• Real-world impact of TTL differences

• Correct configuration and best practices

• Common misconceptions and support escalations

This document is intended for production environments, not beginner setups.

Product / System Overview

Involved Systems

• Cloudflare – Authoritative DNS provider with fixed TTL tiers

• Hostinger – Hosting and email provider recommending specific MX TTL values

• Email transport using SMTP (RFC 5321) and DNS (RFC 1034/1035)

Affected DNS Record Type

• MX (Mail Exchange) records

Technical Background

What Is TTL in DNS?

TTL (Time To Live) defines how long DNS resolvers cache a record before re-querying authoritative name servers.

• TTL is expressed in seconds

• Lower TTL = faster propagation, higher query volume

• Higher TTL = slower changes, better cache efficiency

Cloudflare TTL Architecture (Important)

Cloudflare does NOT allow arbitrary TTL values on most plans.

Supported TTL Buckets (Typical)

➡️ 14400 seconds (4 hours) is NOT available

This is a platform design choice, not a misconfiguration.

Hostinger MX TTL Recommendation Explained

Hostinger documentation typically shows:

TTL: 14400

Key Clarification

• 14400 is a recommendation, not a requirement

• Hostinger mail servers do not enforce TTL validation

• SMTP delivery does not depend on TTL exactness

? RFC standards do not mandate a specific TTL for MX records

Technical Impact Analysis

Does TTL Mismatch Break Email?

No.

Why?

• TTL only affects DNS cache refresh frequency

• Mail servers resolve MX records independently

• Priority and hostname matter — TTL precision does not

Correct Configuration in Cloudflare (Recommended)

Required MX Records for Hostinger

Type: MX
Name: @
Value: mx1.hostinger.com
Priority: 5
TTL: 5 hours (18000)

Type: MX
Name: @
Value: mx2.hostinger.com
Priority: 10
TTL: 5 hours (18000)

Why 5 Hours?

• Closest available value to 14400

• Balanced cache efficiency

• Fully supported by Cloudflare

✅ 2 hours (7200) is also acceptable
❌ Avoid Auto TTL unless explicitly required

Common Errors and Misconceptions

❌ “Hostinger requires exactly 14400”

Root Cause: Misreading UI warnings
Fix: Ignore — informational only

❌ “TTL mismatch causes mail delay”

Root Cause: Confusing TTL with SMTP retry timers
Fix: TTL affects DNS cache, not SMTP queues

❌ “Cloudflare DNS breaks Hostinger mail”

Root Cause: Proxy misunderstanding
Fix: MX records are always DNS-only in Cloudflare

Troubleshooting Checklist

Verify MX Records

dig MX yourdomain.com +short

Expected:

5 mx1.hostinger.com.
10 mx2.hostinger.com.

Verify TTL Returned

dig MX yourdomain.com

Check:

;; ANSWER SECTION:
yourdomain.com. 18000 IN MX 5 mx1.hostinger.com.

TTL ≠ 14400 → Not an issue

Security Considerations

• TTL does not affect:

  • SPF

  • DKIM

  • DMARC

  • TLS (STARTTLS)

• Short TTLs slightly increase DNS query exposure

• Long TTLs delay emergency MX failover

? TTL choice is operational, not security-critical

Best Practices

✔ Use 5 hours TTL in Cloudflare
✔ Keep MX priorities exactly as Hostinger specifies
✔ Do not proxy MX records
✔ Separate DNS, mail, and FTP troubleshooting
✔ Document TTL limitations for support teams

What NOT to Do

❌ Do not migrate DNS just to match TTL
❌ Do not add duplicate MX records
❌ Do not remove working MX records due to TTL warnings
❌ Do not open mail tickets solely for TTL mismatch

Conclusion

A TTL mismatch between Hostinger’s recommended 14400 seconds and Cloudflare’s fixed TTL options is normal, expected, and harmless.

Cloudflare’s 2-hour or 5-hour TTL values are fully compatible with Hostinger mail services and comply with DNS and SMTP standards.

This scenario does not require remediation unless email delivery issues exist for unrelated reasons.

#Cloudflare #Hostinger #DNS #MXRecords #EmailDNS #TTL #ITSupport #SysAdmin #MailServer #SMTP #DNSConfig #CloudflareDNS #HostingerEmail #TechKB #EmailInfrastructure #NetworkEngineering #DomainManagement #DNSIssues #EmailTroubleshooting #RFC #ITOperations #ServerAdmin #EmailSetup #DNSManagement #MailFlow #EmailSystems #CloudHosting #WebHosting #EnterpriseIT #ITKnowledgeBase #CloudDNS #EmailDelivery #DNSArchitecture #MailSecurity #ITBestPractices #TechSupport #DNSResolution #EmailAdmin #HostingSupport #Infrastructure #EmailOps #CloudInfra #DNSRecords #MailRouting #EmailEngineering #HostingTech