What Can I Do If a Record Set Does Not Take Effect?

Symptom

When you ping the domain name, no IP address is returned. There are many causes why a domain name cannot be resolved.

• The causes here are described in order of how likely they are to occur.

  Check these causes one by one until you find the cause of the fault.

  1. Checking the Status of the Domain Name: If the domain name has expired or is abnormal, it cannot be resolved.
  2. Checking the DNS Servers of the Domain Name: If non-Huawei Cloud DNS servers are used for the domain name, the domain name cannot be resolved.
  3. Checking the Record Set: If the record set is incorrect, the domain name cannot be resolved.
  4. Checking the DNS Server Changes Within 24 Hours: Local DNS server caches the NS record configured for the domain name. It may take 48 hours to update the NS record.
  5. Checking the Authoritative DNS Server: Run nslookup to check whether the record set takes effect on the authoritative DNS server.
  6. Submitting a Service Ticket

Checking the Status of the Domain Name

A domain name is the entry for DNS resolution. You can use DNS for resolution only if the status of your purchased domain name is normal. If the domain name is in the serverhold state, for example, the domain name is in arrears, the real name is not authenticated, or the domain name is disputed, the domain name cannot be resolved.

Checking the DNS Servers of the Domain Name

The DNS service provides authoritative DNS servers for domain resolution.

If non-Huawei Cloud DNS servers are configured, the domain name cannot be resolved.

Checking the Record Set

1. Log in to the DNS console and check the zone status.

   If the status is Disabled, the domain name cannot be resolved.

2. Check whether the record set is correct and its status is Normal.

   For example, if the subdomain cannot be accessed, a possible cause is that a record set is added for the second-level domain name but no record set is added for www.

Checking the DNS Server Changes Within 24 Hours

The changes the DNS servers do not take effect immediately. Domain name registrars usually set the TTL value in the NS record to 48 hours. If the local DNS server caches the NS record of the domain name, the changes will take effect in 48 hours.

Consult the domain name registrars for specific cache duration. Do not delete original record sets until the changes take effect to ensure your service continuity.

Checking the Authoritative DNS Server

Check whether record sets of the domain name have taken effect on the authoritative DNS server:

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

If the authoritative DNS server is ns1.huaweicloud-dns.cn and the domain name is example.com, run the following command:

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

If a domain name can be resolved by the authoritative DNS server but the IP address is not returned when the domain name is used for access, the local DNS server may be hijacked. Run either command to check whether public DNS resolution has taken effect: nslookup -qt=[Record set type] [Domain name] 8.8.8.8 or nslookup -qt=[Record set type] [Domain name] 114.114.114.114

If public DNS resolution takes effect, change the local DNS server to a public DNS server, for example, 8.8.8.8 or 114.114.114.114.

Submitting a Service Ticket

If the website still cannot be accessed, create a service ticket for help.