Choorai
KO EN
Common after initial deployment

Fixing DNS NXDOMAIN Errors

Seeing DNS_PROBE_FINISHED_NXDOMAIN in browser? DNS records may be missing or not fully propagated yet.

TL;DR

1) Check domain typos 2) Verify A/CNAME records 3) Run dig against public resolvers 4) Wait for TTL propagation

심각

DNS_PROBE_FINISHED_NXDOMAIN

원인

DNS cannot resolve the requested host. Common causes are missing records, typo in host, or incorrect nameserver delegation.

해결책
  1. Verify domain and subdomain spelling
  2. Confirm A/CNAME records exist
  3. Check registrar nameserver delegation
  4. Allow propagation time based on TTL

Diagnostic steps

terminal
dig your-domain.com

dig @1.1.1.1 your-domain.com

dig @8.8.8.8 your-domain.com

Cloudflare record example

DNS records
Type    Name    Content             Proxy
A       @       203.0.113.10        DNS only
CNAME   www     your-domain.com      Proxied

Important

Avoid conflicting records and remember DNS propagation may take time depending on TTL and resolver cache.

Prerequisites

  • You know the exact domain/subdomain and target A or CNAME value.
  • You have access to your DNS provider console.
  • You can run dig or nslookup from terminal.

Validation

  1. Authoritative DNS returns expected A/AAAA/CNAME records.
  2. Public resolvers (8.8.8.8, 1.1.1.1) return the same answers.
  3. Browser no longer shows NXDOMAIN and reaches your service.

Troubleshooting

  • Double-check typos in hostnames.
  • Avoid conflicting records (e.g., invalid A+CNAME combinations).
  • Account for TTL/propagation delay before concluding failure.

References

Related Articles

Domain & DNS

Core DNS concepts

SSL Certificate Error

HTTPS/TLS issues

Last updated: February 22, 2026 · Version: v0.0.1

Send Feedback

Opens a new issue page with your message.

Open GitHub Issue