No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FusionCloud Troubleshooting Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Domain Names on the Tenant VMs Cannot Be Resolve

Domain Names on the Tenant VMs Cannot Be Resolve


Domain names on the tenant VMs cannot be resolved.

Possible Causes

  • An incorrect DNS server address is configured in the /etc/resolv.conf file on the tenant VMs.
  • Networks between the tenant VMs and the DNS-TENANT nodes are disconnected.
  • The DNS process is abnormal.

Troubleshooting Process

Locate the fault based on the possible causes and troubleshoot the fault.


  1. Check whether you can log in to the TDNS-TNTP01 and TDNS-TNTP02 VMs where DNS is located.

    • If yes, go to 4.
    • If no, go to 2.

  2. Restore the VM. For details, see Cloud Service Management Plane Fault Diagnosis.
  3. Contact technical support to reinstall DNS. No further action is required.
  4. Use PuTTY to log in to the faulty node using the IP address and the service account of the node.

    The default username is udns, and the default password is Huawei12#$.

  1. Run the following command to open the configuration file /etc/resolv.conf:

    vi /etc/resolv.conf

  2. Check whether the two IP addresses in the configuration file are the DMZ_Tenant IP addresses of the DNS-TENANT nodes.

    • If yes, go to 7.
    • If no, correct the IP addresses and perform the test again. If the domain name can be resolved, the fault is rectified. Otherwise, go to 7.

  3. Run the following command on the faulty node to test the network connection between the faulty node and the DNS-TENANT node:

    ping DMZ_Tenant IP address of the DNS-TENANT node

    • If yes, the network connection is normal. Skip 8 and 9.
    • If no, the network connection is abnormal. Go to 8.

  4. Use PuTTY to log in to a DNS-TENANT node as the udns user. Run the following command, and enter the password of the root user to switch to the root user (the default password is Cloud12#$):

    sudo su - root

  5. Run the following command to check whether a route is configured between the tenant VM network external_relay_network and the DMZ_Tenant:

    route -n

    • If yes, contact technical support to rectify the network fault.
    • If no, go to 10.

  6. Enter http://DMK floating IP address:8443 in the address bar of the browser to log in to DMK.

    The default account is udns. The default password is cnp200@HW.

  7. In the navigation pane on the left, choose Deploy Guide.
  8. On the Service Configuration page, click the Services tab and select DNS-Internal.
  9. Set the following parameters:

    • Select Version: version of the installation package
    • Select Action: Config TENANT-DNS Gateway
    • Select Region: local
    • Host Repository: NO
    • Gray Deployment: NO

  10. Click Next to switch to the Hosts and User Configuration page.
  11. Select the DNS-Internal team and the udns account.
  12. Modify the route configuration according to the template.

  13. Click Execute to start the configuration.
  14. Check the task status.

    1. In the navigation pane on the left, choose Task Board.
    2. Locate the task and view the status before the task name. The task is successful if the status changes to .
    3. Click Details in the Operation column to view task details.

  15. Repeat 9 to check the route configuration. If the network recovers, go to 20.
  16. Log in to the DNS-TENANT node and run the following command to check the named process status:

    systemctl status named

    If information similar to the following is displayed, the named process stops accidentally.

  17. Run the following command to restart the named process:

    systemctl restart named

    • If no command output is displayed, the named process is successfully restarted. Run the following command to check the status of the named process:

      systemctl status named

      If information similar to the following is displayed, the named process is restored.

    • If the following information is displayed, the named process fails to restart:
      Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.

      Run the following commands to restore the named process based on the error message:

      systemctl status named

      journalctl -xe

      After the fault is rectified, restart the named process again. If the fault persists, contact technical support for assistance.

Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23173

Downloads: 37

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next