How Do I Check Whether a Record Set Has Taken Effect?

When Will a Record Set Take Effect After It Is Added?

A record set takes effect after it is synchronized to the DNS servers.

• If you add a record set, it takes effect immediately after being added.
• If you modify a record set, the effective time will not be later than the TTL value set in the record set before the modification. For example, if the TTL value is 300s, the new record set will take effect within 300s. If there is no cache delay on the local DNS server, the modification takes effect immediately.

  If the carrier forcibly sets a longer cache duration for domain name records, the modification to or deletion of the records will be delayed for a maximum of 48 hours. During the modification, ensure that the IP addresses before and after the modification can provide services properly.

How Do I Check Whether a Record Set Has Taken Effect?

Pinging the Domain Name (Windows and Linux)

1. On your local host, click the search icon and enter cmd to open the CLI.
2. Run the following command to check whether the record set is taking effect:

   ping [Domain name]

   For example, if the domain name is example.com, run ping example.com.

   If the displayed IP address is the same as the IP address configured in the record set, the record set has taken effect.

   

   When you run the ping command, the domain name can be pinged does not mean that the record set has taken effect. If the displayed IP address is the same as the configured IP address, the record set is taking effect.

Running nslookup (Windows and Linux)

• A record set: maps a domain name to one or more IP addresses
  1. On your local host, click the search icon and enter cmd to open the CLI.
  2. Run the following command to check whether the record set is taking effect:

     nslookup -qt=a [Domain name]

     or

     nslookup [Domain name]

     Example: nslookup example.com

     If the displayed IP address is the same as the IP address configured in the record set, the record set has taken effect.

• CNAME record set: used for scenarios that involve Content Delivery Network (CDN), WAF, and CloudSite
  1. On your local host, click the search icon and enter cmd to open the CLI.
  2. Run the following command to check whether the record set is taking effect:

     nslookup -qt=cname [Domain name]

     Example: nslookup -qt=cname examplesite.com

     If the displayed domain name is the same as that configured in the record set, the record set has taken effect.

• MX record set: used for mail servers
  1. On your local host, click the search icon and enter cmd to open the CLI.
  2. Run the following command to check whether the record set has taken effect:

     nslookup -qt=mx [Domain name]

     Example: nslookup -qt=mx example123.com

     If the displayed mailbox address is the same as that configured in the record set, the record set is taking effect.

• NS record set: used to specify the DNS servers
  1. On your local host, click the search icon and enter cmd to open the CLI.
  2. Run the following command to check whether the record sets are taking effect:

     nslookup -qt=ns [Domain name]

     Example: nslookup -qt=ns example123.top

     If the displayed DNS servers are the same as those provided by DNS service provider, the record set has taken effect.

• Domain name resolution on an authoritative DNS server
  1. On your local host, click the search icon and enter cmd to open the CLI.
  2. Run the following command to check whether the record set is taking effect:

     nslookup -qt= [Record set type] [Domain name] [Authoritative DNS server]

     Example: nslookup -qt=a example123.com ns1.huaweicloud-dns.cn

     The record set configured for example123.com has taken effect on the authoritative DNS server ns1.huaweicloud-dns.cn.

Common Issues

• If the IP address cannot be obtained during the verification, the record set has not taken effect or has been modified. Rectify the fault by referring to Why Did My Record Set Not Take Effect?
• An expired domain name has been renewed, but the website still cannot be visited.

  A possible cause is that the DNS settings are not refreshed. Run ipconfig /flushdns to refresh the settings. Alternatively, wait until the DNS settings are updated and try again.

• The ping command has proved that the domain name can be resolved, but the website cannot be visited.

  Ensure that the domain name is correctly bound to the ECSs where the website is deployed or the website has been licensed. Refer to the following to address the issue:

  Why Can't I Access the Website Even Though the Domain Name Has Been Resolved Successfully?