BREAKING: Cloudflare MINOR 🟡 .AL Domain Resolution Issues – Workarounds Inside

Cloudflare experiencing partial disruption affecting .AL domain resolution. Immediate workarounds and monitoring guidance for indie hackers.

INCIDENT ALERT: Cloudflare .AL Domain Resolution Issues

Status: MINOR – Partial Disruption (Monitoring) Affected Service: Cloudflare DNS Resolution Impact Scope: .AL (Albania) Top-Level Domain Last Updated: Now

---

What's Down & Who's Affected

Cloudflare is reporting resolution issues specifically for domains using the .AL country-code TLD. This means:

Direct impact: Projects using .AL domains proxied through Cloudflare

Symptom: DNS queries timing out or returning SERVFAIL responses

Geographic scope: Global – affects all users attempting to resolve .AL domains

Current status: Not a complete outage, but degraded performance and intermittent failures

If your indie project uses a .AL domain (common for Albania-based founders), your site may be unreachable or experiencing slow DNS propagation right now.

---

Immediate Workarounds – Do This Now

1. Switch DNS Temporarily

If you own the domain registrar account:

Update nameservers to your domain registrar's defaults (or another DNS provider like Route53, Google Cloud DNS, or Quad9)

Propagation typically takes 15-30 minutes

This bypasses Cloudflare entirely for DNS resolution

2. Use Direct IP Access

If you know your origin server's IP, access it directly: http://[YOUR_IP] (note: HTTPS will fail without hostname verification)

Useful for emergency access while DNS recovers

3. Point to Secondary DNS

If using multiple DNS providers, activate your secondary immediately

Cloudflare's secondary NS records should still work via fallback routes

4. Enable Cloudflare Caching Override

In Cloudflare dashboard → Caching → Cache Everything with custom TTL

For .AL domains, temporarily reduce TTL to 60 seconds once resolution returns

---

How to Check If You're Affected

```bash

Run this in terminal

nslookup yourdomain.al

Or use Cloudflare's own resolver

dig yourdomain.al @1.1.1.1

Expected output: Should resolve to your origin IP

If you see: SERVFAIL or timeout → You're affected

```

Alternatively, use online tools:

whatsmydns.net – Check global DNS propagation

mxtoolbox.com – Verify DNS records across multiple resolvers

Cloudflare Status Dashboard – status.cloudflare.com for official updates

---

Alternative DNS Providers to Consider

If you need redundancy or a temporary switch:

1. Route53 (AWS) – $0.40/hosted zone/month + query costs 2. Google Cloud DNS – $0.20/zone/month 3. Quad9 – Free, privacy-focused 4. ns1.com – $24/month, great failover capabilities 5. Your Registrar's DNS – Usually free (GoDaddy, Namecheap, etc.)

---

Monitor Recovery in Real-Time

Set up active monitoring NOW:

Cloudflare Status Page: Watch status.cloudflare.com for .AL TLD updates

Uptime Monitor: Use Pingdom, UptimeRobot, or Betterstack to alert when resolution returns

DNS Propagation Check: Rerun dig commands every 5 minutes

Twitter/Discord: Follow @Cloudflare and their incident channels for updates

Expected recovery time: Cloudflare typically resolves DNS-level incidents within 2-4 hours. Monitor status.cloudflare.com for ETA.

---

Bottom Line

If you're using .AL domains, act now: either switch DNS providers temporarily or access your infrastructure directly. This is not a Cloudflare-wide outage—it's isolated to .AL TLD resolution. Most indie hackers outside that region are unaffected.

Stay calm. Monitor. Switch if needed. Recovery is likely within hours.

Check your domain. Now.