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

Reminder

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

upgrade

OceanStor 9000 V300R006C00 Object Storage Service (Compatible with OpenStack Swift APIs) Administrator Guide 07

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).
Connecting to the External DNS Server (Linux)

Connecting to the External DNS Server (Linux)

This section uses SUSE Linux Enterprise Server 10 and BIND 9 as examples to explain how to connect to the external DNS server.

Prerequisites

You have configured the domain name of the object storage service (compatible with OpenStack Swift APIs).

Context

  • The DNS IP addresses of the object storage service (compatible with OpenStack Swift APIs) consist of the front-end service IP addresses of the primary and secondary nodes, four in total.

  • Two methods are available to connect to the external DNS server: conditional forwarder and delegation. Choose a suitable method based on the following conditions:

    • When the external DNS server is provided by the customer and the domain name of the object storage device (compatible with OpenStack Swift APIs) does not indicate a subdomain of an existing domain configured by the customer, configure a conditional forwarder for the DNS server. For example, if the domain name of the object storage service (compatible with OpenStack Swift APIs) is example.com, a conditional forwarder can forward domain name requests sent by the DNS server to OceanStor 9000. Then, OceanStor 9000 returns the front-end service IP address of the node to the client.
    • When the external DNS server is provided by the customer, domains have been configured, and the domain name of the OceanStor 9000 object storage service (compatible with OpenStack Swift APIs) indicates a subdomain of an existing domain configured by the customer, create a delegation for the DNS server. For example, when the customer has configured domain test.com, the domain name of the object storage service (Compatible with OpenStack Swift APIs) is example.test.com, create a delegation for the DNS server.
  • OceanStor 9000 supports IPv4 and IPv6 DNS servers.

Procedure

  • Creating a conditional forwarder for the DNS server

    All parameter values used in the following operations are example values. The IP address can be either an IPv4 address or an IPv6 address. Configure values based on site requirements.

    1. Log in to the DNS server as a user having administrator rights.
    2. Run vim /etc/named.conf to edit the configuration file. Press i to go to the edit mode and type the following content. Then enter :wq and press Enter to save and exit.

      zone "example.com" in {
      	type forward;
      	forwarders { 192.168.0.200;192.168.0.201;192.168.0.202;192.168.0.203;};
      };
      
      Parameter description:
      • /etc: path where the named.conf configuration file resides. The path varies depending on which operating system you use. Generally, the configuration file resides in the /etc directory.
      • example.com: domain name of the object storage service (compatible with OpenStack Swift APIs)
      • 192.168.0.200, 192.168.0.201, 192.168.0.202, and 192.168.0.203: four DNS IP addresses of object storage service (compatible with OpenStack Swift APIs)

    3. Run service named restart to restart the named service for the setting to take effect.

      [root@ISM 16:57:15 /var/lib/named]# service named restart
      Shutting down name server BIND waiting for named to shut down (28s)done
      Starting name server BIND                                          done

    4. Run exit to log out.
  • Creating a delegation for the DNS server

    All parameter values used in the following operations are example values. The IP address can be either an IPv4 address or an IPv6 address. Configure values based on site requirements.

    1. Log in to the DNS server as a user having administrator rights.
    2. Run vim /etc/named.conf to edit the configuration file. Press i to go to the edit mode and type the following content. Then enter :wq and press Enter to save and exit.

      zone "test.com" in {
      	type master;
      	file "test.zone";
      };
      Parameter description:
      • test.com: DNS domain name.
      • test.zone: DNS zone name.
      • /etc: path where the named.conf configuration file resides. The path varies depending on which operating system you use. Generally, the configuration file resides in the /etc directory.

    3. Run vim /var/lib/named/test.zone to edit the zone file and add the delegation setting.

      $TTL 86400
      $ORIGIN test.com.
      @       IN      SOA     ds.test.com. root.test.com.  (
                                            200601     ; Serial
                                            28800      ; Refresh
                                            14400      ; Retry
                                            3600000    ; Expire
                                            86400 )    ; Minimum
                      IN      NS     ds.test.com.
                      IN      MX      20      mail.test.com.
      example   IN      NS      hostexample
      hostexample    IN      A       192.168.0.200
      hostexample    IN      A       192.168.0.201
      hostexample    IN      A       192.168.0.202
      hostexample    IN      A       192.168.0.203
      
      Parameter description:
      • example: part of the domain name of the object storage service (compatible with OpenStack Swift APIs) excluding the parent domain name
      • hostexample: name of the delegated host. The host name is self-definable and cannot conflict with OceanStor 9000 domain names.
      • /var/lib/named: path where the test.zone configuration file resides. The path varies depending on which operating system you use. Generally, the configuration file resides in the /var/lib/named directory.
      • 192.168.0.200: DNS IP address of the object storage service (compatible with OpenStack Swift APIs)
      • 192.168.0.201: DNS IP address of the object storage service (compatible with OpenStack Swift APIs)
      • 192.168.0.202: DNS IP address of the object storage service (compatible with OpenStack Swift APIs)
      • 192.168.0.203: DNS IP address of the object storage service (compatible with OpenStack Swift APIs)

    4. Run service named restart to restart the named service for the setting to take effect.

      [root@ISM 16:57:15 /var/lib/named]# service named restart
      Shutting down name server BIND waiting for named to shut down (28s)done
      Starting name server BIND                                          done

    5. Run exit to log out.

Exception Handling

When connecting to the external DNS server in delegation mode, if the client fails to access the OceanStor 9000 using a domain name, check whether network connectivity is normal and delegation is correctly configured. If network connectivity is normal and delegation is correctly configured, do the following:
  1. Run cat /etc/named.conf to check whether a forwarder is configured in options in the configuration file or in the root zone. The command output is as follows:

    Configuring a forwarder in options

    options {
    
    	# The directory statement defines the name server's working directory
    
    	directory "/var/lib/named";
    
    	dump-file "/var/log/named_dump.db";
    	statistics-file "/var/log/named.stats";
      forwarders{
          192.168.0.100;
      };
      forward first;
    };

    Configuring a forwarder in the root zone

    zone "." IN {
       type forward;
       forward only;
       forwarders{
       192.168.0.100;192.168.0.150};
    };
    • If yes, confirm with the customer's DNS maintenance administrator whether the domain names of the current zone and other zones can be resolved after the forwarder is blocked. After the forwarder is blocked, a domain name request is resolved only in the current zone but will not be forwarded to another zone or DNS server. If the domain names of the current zone and other zones can be resolved after the forwarder is blocked, go to 2. If it is unable to ensure whether the domain names of the current zone and other zones can be resolved after the forwarder are blocked, contact technical support engineers.
    • If no, contact technical support.

  2. Run vim /etc/named.conf to edit the configuration file. Press i to go to the edit mode. Forwarders can be blocked in the current zone after you type the following content. Then enter :wq and press Enter to save and exit.

    zone "test.com" in {
    	type master;
    	file "test.zone";
      forwarders{};
    };
    NOTE:

    After the forwarder is blocked, a domain name request is resolved only in the current zone but will not be forwarded to another zone or DNS server, preventing a domain name resolution failure.

  3. Check whether the client can access OceanStor 9000. If the access fails, contact technical support engineers.
Translation
Download
Updated: 2019-04-28

Document ID: EDOC1000122524

Views: 10685

Downloads: 86

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