DNS issues are the most common source of custom domain problems. The good news? They're usually straightforward to fix once you know what to look for.

✅ Confirm You Have the Required Records

Your domain needs exactly two DNS records to point to Nuviw:

1. A Record (Root Domain)

Host/Name: @ (or blank, or your domain name)

Type: A

Value: The IP address from Nuviw (e.g., 76.76.21.21)

2. CNAME Record (www Subdomain)

Host/Name: www

Type: CNAME

Value: The hostname from Nuviw (e.g., cname.nuviw.app)

❌ Common DNS Mistakes & How to Fix Them

Problem 1: Multiple A Records for Root

Symptom: Your site loads sometimes but not always, or loads different content.

Cause: You have 2+ A records pointing @ to different IPs (e.g., Nuviw + old host).

Fix:

Log into your registrar's DNS settings

Find all A records for the root (@)

Delete all except the one pointing to Nuviw's IP

Problem 2: Mixing A and CNAME on Same Host

Symptom: DNS verification fails or site won't load.

Cause: You have both an A record AND a CNAME record for the same hostname.

Fix:

Use A records ONLY for the root domain (@)

Use CNAME records ONLY for subdomains (www, blog, etc.)

Never put both types on the same host—it violates DNS standards

Problem 3: Typos in DNS Values

Symptom: Site doesn't load, DNS verification fails.

Cause: Missing digit in IP, extra space, wrong hostname.

Fix:

Copy-paste the values directly from Nuviw (don't retype manually)

Double-check for trailing spaces or periods

IP addresses should be 4 numbers separated by dots (e.g., 76.76.21.21)

Problem 4: Cloudflare Proxy Enabled

Symptom: DNS verifies but SSL fails, or site shows Cloudflare errors.

Cause: Orange cloud icon (proxy) is active in Cloudflare.

Fix:

Log into Cloudflare

Go to DNS settings

Click the orange cloud next to your A/CNAME records

Turn it gray ("DNS only" mode)

Wait for Nuviw SSL to be issued

You can re-enable proxy after SSL works

Problem 5: Old Records Not Deleted

Symptom: Sometimes loads old site, sometimes new Nuviw site.

Cause: You added Nuviw records but didn't delete old host records.

Fix:

Find ALL A and CNAME records in your DNS settings

Delete any pointing to your old hosting provider

Keep ONLY the records pointing to Nuviw

⏱️ DNS Propagation: What to Expect

Even with correct records, changes take time to spread globally:

Typical Timeline

5-15 minutes: Some locations start seeing changes

1-2 hours: Most of the world has updated

24-48 hours: 100% global propagation (worst case)

How to Check Propagation Status

whatsmydns.net — Visual map showing propagation globally

dnschecker.org — Check specific record types

Terminal command: dig yourdomain.com (shows current DNS response)

🛠️ Advanced Debugging

Using Terminal/Command Line

Check A record:

dig example.com A

Should return Nuviw's IP address.

Check CNAME record:

dig www.example.com CNAME

Should return something like cname.nuviw.app.

Check all DNS records:

dig example.com ANY

Using nslookup (Windows)

nslookup example.com

📞 When to Contact Support

Reach out to Nuviw support if:

✓ Your DNS records match Nuviw's requirements exactly

✓ DNS propagation shows green checkmarks globally

✓ It's been more than 48 hours

✓ Your site still doesn't load or shows errors

Include in your support request:

Your domain name

Your domain registrar (GoDaddy, Namecheap, etc.)

Screenshots of your DNS settings

Screenshot from whatsmydns.net showing propagation

Any error messages you're seeing

✅ Quick DNS Checklist

✓ ONE A record for @ pointing to Nuviw's IP

✓ ONE CNAME record for www pointing to Nuviw's hostname

✓ No old/conflicting records

✓ No typos in IP address or hostname

✓ Cloudflare proxy disabled (gray cloud) during setup

💡 Pro Tip

95% of DNS issues are solved by deleting old records and waiting for propagation. Before trying complex solutions, make sure you've removed ALL old DNS entries from your previous hosting provider.