Configuring a DDNS policy

A DDNS policy contains the DDNS server address, port number, login ID, password, time interval, associated SSL client policy, and update time interval. After creating a DDNS policy, you can apply it to multiple interfaces to simplify DDNS configuration.

The URL address for update requests varies by DDNS server.

Identify the DDNS server type in your network and following the following restrictions and guidelines to set an appropriate URL address:

• The URL address for an update request can start with:

  • http://—The HTTP-based DDNS server.

  • https://—The HTTPS-based DDNS server.

  • ods://—The TCP-based ODS server.

  • gnudip://—The TCP-based GNUDIP server.

  • oray://—The TCP-based PeanutHull DDNS server.

• HP and GNUDIP are common DDNS update protocols. The server-name argument is the domain name or IP address of the service provider's server using one of the update protocols.

• The port number in the URL address is optional. If no port is specified, the system uses the default port numbers: port 80 for HTTP, port 443 for HTTPS, and port 6060 for PeanutHull DDNS server.

• The <h> value can be automatically filled with an FQDN if it is specified in the command for applying a DDNS policy to an interface. The <a> value is automatically filled with the primary IP address of the interface to which the DDNS policy is applied. For more information about applying DDNS policies, see "Applying the DDNS policy to an interface."

• You can also manually specify an FQDN and an IP address for the <h> and <a> fields. In this case, the FQDN specified at the CLI does not take effect. As a best practice, do not manually change the <h> and <a> because your configuration might be incorrect.

• No FQDN or IP address can be specified in the URL address for update requests sent to the PeanutHull DDNS server. You can specify the FQDN when applying the DDNS policy to an interface. The IP address is the primary IP address of the interface to which the DDNS policy is applied.

Visit the website of a DDNS service provider, register an account, and apply for a domain name for the DDNS client. When the DDNS client updates the mapping between the domain name and the IP address through the DDNS server, the DDNS server checks the following:

• Whether the account information is correct.

• Whether the domain name to be updated belongs to the account.

1. Enter system view.

   system-view

2. Create a DDNS policy and enter its view.

   ddns policy policy-name

3. Specify a URL address for DDNS update requests.

   url request-url

   By default, no URL address is specified for DDNS update requests.

   The URL address cannot contain a username or password. To configure them, use the username command and the password command.

4. Specify the username for logging in to the DDNS server.

   username username

   By default, no username is specified.

5. Specify the password for logging in to the DDNS server.

   password { cipher | simple } string

   By default, no password is specified.

6. (Optional.) Specify the parameter transmission method for sending DDNS update requests to HTTP/HTTPS-based DDNS servers.

   method { http-get | http-post }

   By default, the http-get method is used.

   This step is effective for communicating with HTTP/HTTPS-based DDNS servers.

   Specify the http-post keyword for DDNS update with a DHS server.

7. (Optional.) Associate an SSL client policy with the DDNS policy.

   ssl-client-policy policy-name

   By default, no SSL client policy is associated with the DDNS policy.

   This step is only effective and a must for HTTP-based DDNS update requests. For SSL client policy configuration, see Security Configuration Guide.

8. (Optional.) Specify the interval for sending update requests.

   interval days [ hours [ minutes ] ]

   By default, the time interval is one hour.