DNS
Contents
    加载中
Support DNS DNS Resolution Effect

DNS Resolution Effect

What should I do if DNS resolution does not work?

  1. Confirm the domain validity period: the expiration of the domain will invalidate DNS resolution. You need to check the domain expiration time at your registrar. If it has expired, please renew it as soon as possible. After it is successfully renewed, DNS resolution will return to normal in 0–72 hours.
  2. Confirm the DNS server of the domain: please check at your domain registrar whether the DNS server has been changed to DNS specified by DNSPod; if not, DNS resolution will be affected. If the server has already been changed to the DNS server of DNSPod, please wait patiently, as the record will take effect globally in 0–72 hours.
  3. Confirm record configuration: you need to check whether you have configured relevant records at your DNS service provider, such as the commonly used A and CNAME records; if not, DNS resolution will not work. For more information on the DNS service of DNSPod, please see Settings of Various Record Types.

Node:

  • If DNS resolution doesn't work for only certain users, please check whether the default split zone is selected in the configuration (which is required); if not, users in certain zones may not be able to access the domain.
  • If your domain is only configured with a record of a specified split zone, then only users in this split zone can access your domain, while all other users cannot. For more information, please see Split Zone Description.

How do I test whether a record is effective?

You can use related commands for troubleshooting. After confirming that a DNS record was configured more than 72 hours ago, click Start > Search in the bottom-left corner on Windows and enter CMD to open the command prompt.

Run the ping command to verify whether a record is effective

    1. Enter ping + space + your domain (www.dnspod.com is used as an example here).
    1. After you press Enter, if the displayed IP is the same as the IP in the record you set as shown below, it means that the record has taken effect.

Run the nslookup command to query record information

    1. To query the local DNS resolution result, run nslookup domain
    1. To query the CNAME record of a domain (a CNAME record should have been configured), run nslookup -q = cname domain
    1. To query the MX record of a domain (an MX record should have been configured, which is used to specify the email server address), run nslookup -q = mx domain
    1. To query the NS record of a domain (an NS record should have been configured, which is used to specify the email server address), run nslookup -q = ns domain
    1. To check whether the domain is hijacked, perform the following tests:
      nslookup domain
      nslookup domain 119.29.29.29

Node:
If the record is normal during the test when you specify 119.29.29.29 but resolves to an incorrect IP when you don't specify 119.29.29.29, it can be basically judged that the domain is hijacked. In this case, you need to contact the ISP redirected to for assistance.

During the transfer of DNS service to DNSPod, why can't the website be opened at all or in certain zones?

In the process of DNS service transfer, different top-level domains may have different TTL settings for DNS servers, so the newly modified DNS record will take effect globally in 0–72 hours. If your DNS address was changed less than 72 hours ago, please confirm the following:

  1. Make sure that the record you set at DNSPod is the same as that at the original DNS service provider; otherwise, this problem may occur.
  2. During this process, if you need to perform related operations (such as adding, modifying, or deleting) on the record, you should do so at both providers to ensure the consistency of the record.

My domain is resolved by DNSPod and no changes were made. Why can't it be accessed suddenly?

  1. Please check with your registrar whether your domain expired.
  2. If you have purchased a DNS plan for your domain, please check whether the plan has expired. If it has expired, but the DNS server address has not been changed to the address in the Free plan (DNS address of each plan), your domain's DNS resolution will gradually become invalid. In this case, we recommend you renew the plan as soon as possible or change the DNS server address to a free address 3 days in advance.

The DNS record has taken effect, but why can't I open the website?

If the DNS record has taken effect, but the website cannot be opened, possible reasons include:

  1. Incorrect record configuration:
  • Check whether the host is configured incorrectly; for example, aaa is misspelled as aas.
  • If the default split zone is not set, we recommend you configure it first before configuring other split zones; otherwise, certain users may not be able to access the domain. For more information, please see Split Zone Description.
  • Check whether the IP entered in the record is correct; for example, 11.1.1.1 is written as 11.1.1.11.. You need to contact your server provider for confirmation.
  1. Local DNS cache problem:
    In order to speed up website access, the system will automatically store the websites that have been accessed with IP addresses obtained into the DNS cache of the local computer. When such a website is accessed again, its IP address will be directed taken out of the local DNS cache instead of the DNS server for faster access. Therefore, if there is a problem with the local DNS cache, the website will be inaccessible. You can enter CMD in "Run" and run the command ipconfig /flushdns to flush the local DNS cache.
  2. Host service configuration problem:
    In this case, the cause is generally that the domain is not bound in the configuration according to the requirements of the hosting service provider or the configuration file is incorrect. You can contact the provider for assistance and confirmation..
  3. If there are specific errors such as 502 and 403 when the website is accessed, please contact your website service provider or designer and check the website program according to the error message.

Why can't I get an IP when I run the command to connect to the domain?

There are several reasons why you can't get an IP when running the command ping domain:

  1. The split zone is not selected correctly for the record: if the default split zone is not selected, certain users may not be able to access the domain. For more information, please see Split Zone Description.
  2. The DNS change has not taken effect yet: the change will take effect globally in 0–72 hours, so it won't be fully effective in just a few hours. If your local ISP's DNS server has not completely refreshed your domain record, the IP cannot be pinged.
  3. The DNS record of the domain is cached:
  • On Windows, if you access the internet through a dial-up internet, you can enter CMD in "Run" and then run the command ipconfig /flushdns to flush the local DNS cache.

  • If you access the internet through a router, you need to clear the router's DNS cache. This can be done by rebooting the router, and if the router cannot be rebooted, the DNS server of Windows should be replaced with another address.

Node:

  • After clearing the router cache in this way, you also need to run the command ipconfig /flushdns.
  • Linux and Unix do not cache DNS records. On macOS X, you can run the command killall lookupd to clear the DNS cache.
  1. If there is no problem with the above, please check whether the server configuration is incorrect.

Node:
If anything goes wrong during this process, please contact us.

What should I do if no A record is detected by the domain detection tool?

  1. First, please check whether you have added an A record for the corresponding domain. For more information, please see A Record.
  2. Then, please check whether the checked domain is correct:
  • If your domain is dnspod.com, and the host you entered when adding the A record is "@", then the domain you should check is dnspod.com.
  • If the host you entered when adding the A record is "www", then the domain you should check is www.dnspod.com.

Node:
The detection results of the domain and subdomain are different.

Last updated on 2020-11-23 06:54