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

After a record set is added for a domain name, the record set takes effect only after it is synchronized to the DNS server.

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

  If a carrier forcibly prolongs the cache time of domain name record sets, the effective time will be slightly delayed.

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

Running the Ping Command to Check Whether a Record Set Has Taken Effect (Applicable to Windows or Linux Hosts)

1. On your local host, click the search icon and enter cmd to open the CLI.
2. Run the following commands to check whether the record sets take effect:

   ping Domain name

   For example, to check whether the resolution of domain name example.com has taken effect, run the ping example.com command.

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

Running the nslookup Command to Check Whether a Record Set Has Taken Effect (Applicable to Windows and Linux Hosts)

• Verify an A record set.
  1. On your local host, click the search icon and enter cmd to open the CLI.
  2. Run the following commands to check whether the record sets take 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 takes effect.

• Verify a CNAME record set: Content Delivery Network (CDN), Web Application Firewall (WAF), and CloudSite scenarios.
  1. On your local host, click the search icon and enter cmd to open the CLI.
  2. Run the following commands to check whether the record sets take effect:

     nslookup -qt=cname domain name

     Example: nslookup -qt=cname examplesite.com

     If the displayed CNAME value is the same as that configured in the record set, the record set takes effect.

• Verify a MX record set: It is used to specify the address of a mail server.
  1. On your local host, click the search icon and enter cmd to open the CLI.
  2. Run the following commands to check whether the record sets take 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 takes effect.

• Verify a NS record set: It is used to specify the DNS address of the resolution service provider.
  1. On your local host, click the search icon and enter cmd to open the CLI.
  2. Run the following commands to check whether the record sets take effect:

     nslookup -qt=ns Domain name

     Example: nslookup -qt=ns example123.top

     If the displayed IP address is the same as the DNS address of the service provider, the record set has taken effect.

• Check whether the domain name resolution of a specified authoritative DNS server takes effect.
  1. On your local host, click the search icon and enter cmd to open the CLI.
  2. Run the following commands to check whether the record sets take effect:

     nslookup -qt= Type Domain name Authoritative DNS address

     Example: Run the following command to check whether domain name example.com can be resolved by the authoritative DNS server (ns1.huaweicloud-dns.cn is used as an example):

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

     The record sets of example123.com using authoritative DNS ns1.huaweicloud-dns.cn has taken effect.

FAQ

• If the correct IP address cannot be obtained during the verification, the record set has not taken effect or has been modified. You are advised to 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 opened.

  The possible cause is that the DNS resolution cache is not refreshed. Run the ipconfig /flushdns command to refresh the cache. Alternatively, wait until the DNS is refreshed and try again.

• The ping command has proved that the domain name resolution is normal, but the website cannot be opened.

  Check whether the domain name is correctly bound to the ECS where the website is deployed or whether the website has been licensed. Refer to

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