Common issues

Available in Classic and VPC

You may encounter the following issues while using the Global DNS service. Check the causes and solutions for each issue and take appropriate action.

DNS record edit error

DNS record changes are not applied after editing.
Changes to the IP address of the A record are not reflected after editing.

Cause

• DNS record setting changes take time to apply. Until the new settings are applied, the previous settings may be cached in the DNS record. Depending on the Time To Live (TTL; the refresh cycle for added record information) value specified in the record, previous values may be returned in response to DNS queries. Even if you change the TTL value, the changes do not apply immediately. The previous TTL value remains cached, and the new settings do not apply until the time specified in the previous settings elapses.
• If you do not deploy the record settings to the name server after editing, the changes may not be reflected.

Solution

TTL value setting
Setting the TTL value to the default is recommended. If the TTL value is too low or too high, unintended results may occur.

To edit the TTL value from the NAVER Cloud Platform console, follow these steps:

1. In the NAVER Cloud Platform console, click > Services > Networking > Global DNS > Record in order.
2. Click the [Edit record] button.
3. After editing the TTL value, click the [Apply settings] button at the top of the screen.

To edit the TTL value using API, follow these steps:

1. Edit the TTL value through the record edit API.
2. Deploy through the record application API.

Deploying record changes
To apply record changes to the name server, follow these steps:

1. In the NAVER Cloud Platform console, click > Services > Networking > Global DNS > Record in order.
2. After editing the record, click the [Apply settings] button at the top of the screen.
   • The [Apply settings] button is activated when there are changes.
3. After checking the settings, click the [Deploy] button.

Host response delay

In Linux environments, there are times when the response from hosts registered in the load balancer or DNS is delayed.

Cause

In Linux environments, when accessing a host registered in DNS, the IP of the DNS server host is queried each time. Due to the characteristics of DNS servers, this process may result in delayed responses.

Solution

Using DNS caching allows you to find the host's IP quickly. Installing nscd, a name service client daemon, on Linux allows you to process DNS queries quickly by storing queried content in cache without querying the DNS server each time.

To install and run nscd, follow these steps:

1. Install nscd.

   yum install nscd
   service nscd start
   

2. Run the installed nscd.

   service nscd start
   

3. Register nscd in the startup services to run automatically on reboot.

   chkconfig nscd on
   

Domain unresponsive

The domain is not responding.
The domain fails to respond intermittently.

Cause

Global DNS name servers are not properly set up in the parent registrar.

Solution

Checking domain response
You can check the domain response by directly querying the Global DNS name servers.
The Global DNS name servers are as follows:

• ns1-1.ns-ncloud.com
• ns1-2.ns-ncloud.com

To check the domain response by querying the Global DNS name server, follow these steps:

dig @nameserver <domain> <record type> 

The following is a writing example.

dig @ns1-1.ns-ncloud.com example.com A

Verifying Global DNS name server settings in parent registrar

• If the domain response is still not normal after confirming a normal response by directly querying the Global DNS name server, check if the Global DNS name servers (ns1-1.ns-ncloud.com, ns1-2.ns-ncloud.com) are properly set up in the parent registrar. If the Global DNS name servers are not registered, register them.
• If the name servers other than the Global DNS name servers are registered, delete the other name server information from the parent registrar as they may cause issues when responding.
• If you migrated from another name server to Global DNS, even after removing the other name server from the parent registrar, the existing name server may continue to respond for the duration of the domain TTL. Maintain the domain registered on the existing name server for about a week.

View DS record

Want to view the DS record.

Solution

On the NAVER Cloud Platform console, click the [Registration agency setup information] button in > Services > Networking > Global DNS >Record.

View KEYDATA

Unable to search for the KEYDATA required for DNSSEC registration.

Cause

This is not an error situation. You can check the KEYDATA by directly querying the Global DNS name server.

Solution

Check the KEYDATA by directly querying the Global DNS name server.
The Global DNS name servers are as follows:

• ns1-1.ns-ncloud.com
• ns1-2.ns-ncloud.com

To check the domain response by querying the Global DNS name server, follow these steps:

dig @nameserver <domain> DNSKEY

The following is an example of a query.

dig @ns1-1.ns-ncloud.com example.com DNSKEY

"Register the subdomain after delegating it from the parent domain." message

The message "Register the subdomain [www.example.com] after delegating it from the parent domain [example.com]." appears.

Cause

This error message appears when attempting to register a subdomain without proper delegation.

Solution

To create [www.example.com] as a subdomain rather than a record type while the parent domain [example.com] is already registered, follow these steps:

1. Register the following in the parent domain [example.com].
   • host: www (host to be delegated)
   • type: NS
   • content: register Global DNS name servers for delegation
     • ns1-1.ns-ncloud.com
     • ns1-2.ns-ncloud.com
2. Add the subdomain (www.example.com).

Domain migration between accounts

Unable to transfer a domain registered in Global DNS to another account.
Want to transfer name servers for use with another account.

Cause

Domain migration between accounts is not supported. You must manually delete the domain and recreate it in another account.

Solution

To transfer a domain registered in Global DNS to another account, follow these steps:

1. In the NAVER Cloud Platform console, click > Services > Networking > Global DNS > Record in order.
2. Click the domain and click the [Download] button.
   • An Excel file containing domain information downloads.
3. Open the downloaded Excel file, delete records with type "SOA" and "NS," then save.
   • If using LB records to integrate with LB VPC or LB Classic, register as CNAME. Open the Excel file, edit the LB usage status to "N" for records with type "CNAME" or "LB," then save.
4. Delete the records in the console and delete the domain.
5. Log out of the console.
6. Log in with the account you want to transfer the domain to, and in the NAVER Cloud Platform console, click > Services > Networking > Global DNS > Record in order.
7. Click the [Upload] button.
8. Upload the Excel file saved in step 2.