English

বাংলা
हिन्दी

English

বাংলা
हिन्दी

Appearance

DNS not resolving ​

Symptoms ​

  • The browser says the server cannot be found, or the address does not resolve.
  • The site works for some networks but not for others.
  • A new domain does not open at all, even after you expected it to be live.

Common causes ​

  • The domain's DNS records were never created, or were created at the wrong DNS provider.
  • A recent change has not finished spreading, because of the TTL.
  • The nameservers at the registrar do not match the DNS provider where the records are.
  • A spelling mistake in the host or value.

Safe initial checks ​

  1. Look up the nameservers: dig NS yourdomain.com +short.
  2. Look up the address: dig A yourdomain.com +short.
  3. Compare the answers with the DNS provider you identified in Find your DNS provider.
  4. Wait if the change was made recently.

These checks only read data, so they are safe to run at any time.

Step-by-step solutions ​

  1. Records missing. Add the A record for the domain at the correct provider. See A and AAAA records.
  2. Wrong provider. Edit the records at the provider the nameserver lookup names, not at a different one.
  3. Nameservers mismatch. Correct the nameservers in the Client Area, or ask support if the option is not shown. See Change nameservers.
  4. Spelling error. Correct the host and value exactly, then check again.

How to confirm the issue is fixed ​

  • dig A yourdomain.com +short returns the expected address from more than one network.
  • The site opens in a browser.

When to contact support ​

Contact support if the nameserver lookup returns nothing, if the nameservers do not match any account you have, or if you cannot find the DNS editor.

Information to include in a support ticket ​

  • The domain name, and the output of dig NS and dig A.
  • When you last changed the nameservers or the records.

Last reviewed ​

2026-10-27