Creating Service Records for Generic Provider (DynDNS)

Stacks Image 179
The screen shot above depicts a service record example for the Generic Provider (DynDNS). This is similar to the Generic Provider (Regex). In fact, the first section is identical, and the second section is hard-coded.

  • Construction of the URL to update a dynamic DNS record
    This is defined by using two text fields

    • Update URL
      The HTTP URL string that includes all query parameters. Within this string, you can use the "<ip>" substring (without double qoutes) as a placeholder for IPv4 or IPv6 public address. This UTF8 encoded string must not be "percent encoded". Only the GET method is supported.

      To create this string, you have to search for your dynamic DNS provider's "Update API". Then, manually construct this URL. You need to have basic knowledge of HTTP protocols and how query parameters are specified. If you need technical assistance, please do not hesitate to get in touch with our support team.

    • Authorization
      Most, but not all, APIs pass the credentials in a Authorization header. The most commonly used Authorization header is the "Basic" authorization. Please use web tools to create your Authorization header value, like this web site. If an Authorization header is not needed, then simply enter "none" in this field.
  • Checking Status
    Almost 50% of all dynamic DNS providers use the "Dynamic DNS Update API" developed by DynDNS. Checking update status and reporting errors on this API is not trivial. Hence, we are offering this variant of Generic Provider to support the providers that utilize the DynDNS API.