HP MSR2000/3000/4000 Router Series Layer 3 - IP Services Command Reference

120
DDNS server URL addresses for DDNS u
p
date re
q
uests
DYNDNS
http://members.dyndns.org/nic/update?system=dyndns&hostname=<h>&myip=<a
>
DYNS http://www.dyns.cx/postscript.php?host=<h>&ip=<a>
ZONEEDIT http://dynamic.zoneedit.com/auth/dynamic.html?host=<h>&dnsto=<a>
TZO http://cgi.tzo.com/webclient/signedon.html?TZOName=<h>IPAddress=<a>
EASYDNS
http://members.easydns.com/dyn/ez-ipupdate.php?action=edit&myip=<a>&host_i
d=<h>
HEIPV6TB http://dyn.dns.he.net/nic/update?hostname=<h>&myip=<a>
CHANGE-IP http://nic.changeip.com/nic/update?hostname=<h>&offline=1
NO-IP http://dynupdate.no-ip.com/nic/update?hostname=<h>&myip=<a>
DHS
http://members.dhs.org/nic/hosts?domain=dyn.dhs.org&hostname=<h>&hostscmd
=edit&hostscmdstage=2&type=1&ip=<a>
HP https://server-name/nic/update?group=group-name&myip=<a>
ODS ods://update.ods.org
GNUDIP gnudip://server-name
PeanutHull oray://phservice2.oray.net
No username or password is included in the URL address. To configure the username and password, use
the username command and the password command.
HP and GNUDIP are common DDNS update protocols. The server-name parameter is the domain name
or IP address of the service provider's server using one of the update protocols.
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 DDNS server.
members.3322.org and phservice2.oray.net are the domain names of DDNS servers. The domain
names of PeanutHull DDNS servers can be phservice2.oray.net, phddns60.oray.net, client.oray.net,
ph031.oray.net, and so on. Determine the domain name in the URL according to the actual situation.
The port number in the URL address is optional. If no port number is specified, the default port number
is used. HTTP uses port 80, HTTPS uses port 443, and the PeanutHull server uses port 6060.
The system automatically fills <h> with the FQDN that is specified when the DDNS policy is applied to
the interface and automatically fills <a> with the primary IP address of the interface to which the DDNS
policy is applied. You might also manually specify an FQDN and an IP address in <h> and <a>,
respectively. After that, the FQDN that is specified when the DDNS policy is applied becomes ineffective.
However, manual configuration of <h> and <a> is not recommended.
You cannot specify an FQDN and IP address in the URL address for contacting the PeanutHull server.
Alternatively, you can specify an FQDN when applying the DDNS policy to an interface. The system