![]() ![]() Some Top-level Domains (TLDs) accept DNS Public Key (DNSKEY) records instead of Delegation Signer (DS) records.No errors are returned for these attempts they simply remain unchanged. This helps prevent customers from accidentally overwriting their redirects, since the hosts must remain assigned to the redirect server in order to function. ![]() Special note on WebHopsĬurrently, Dynamic DNS (DynDNS Pro) or Dyn Standard DNS hosts assigned to our WebHop servers cannot be updated via our API. system, previously used to identify update typeĪll other parameter names could lead to ignoring your update request with the return code abuse.We will accept these parameters without generating error messages: The !donatorreturn will be used if the account is not credited. This feature is only available to credited users. Parameter is ignored for static DNS hosts. NOCHG could be used to keep current state. YES activates feature and turns on offline redirect for hostname (if set). Parameter is ignored for situations when no MX value is set for host and for Dyn Standard DNS hosts. YES activates preferred MX record pointed to hostname itself, NOCHG keeps the previous value, any other value is considered as NO and deactivates the corresponding DNS record. Requests the MX in the previous parameter to be set up as a backup MX by listing the host itself as an MX with a lower preference value. Specifying an MX of NOCHG will cause the existing MX setting to be preserved in whatever state it was previously updated via a client or the Dyn website. The specified MX must resolve to an IP address, or it will be ignored. Specifies an eMail eXchanger for use with the hostname being modified. Parameter is ignored for Dyn Standard DNS hosts. Any other value will disable wildcard for hosts in update. ![]() NOCHG value will keep current wildcard settings. Parameter enables or disables wildcards for this host. If the IP address passed to the system is not properly formed, it will be ignored and the system’s best guess will be used. If this parameter is not specified, the best IP address the server can determine will be used (some proxy configurations pass the IP in a header, and that is detected by the server). This is a required field.Įach hostname specified will be updated with the same information, and the return codes will be given one per line, in the same order as given. Update Parameter FieldĬomma separated list of hostnames that you wish to update (up to 20 hostnames per request). We might stop processing of POST requests at any time, without notice. Please note that although POST requests are permitted and will be processed, we don’t encourage developers to use them. User-Agent: Company - Device - Version Number GET /nic/update? hostname= yourhostname& myip= ipaddress& wildcard=NOCHG& mx=NOCHG& backmx=NOCHG HTTP/1.0Īuthorization: Basic base-64-authorization Request should be followed by sending an empty line.įragment base-64-authorization should be represented by Base 64 encoded username:password string. Note that there is the bare minimum set of headers. Legacy Authentication URL HTTP GET RequestĪctual HTTP request should look like following fragment. Use commas to separate multiple IP addresses in the myip field. Note: This authentication method supports both IPv6 and IPv4 addresses. See RFC 2616 for information about the HTTP Protocol.įor web-browsers or utility programs (fetch, curl, lwp-request) that can parse authentication section in URL. These examples are provided only as samples. It is not necessary to open any incoming ports (or allow incoming ICMP) for updating.Īll clients must send a well-formed user agent that includes company name, model number, and software build revision. Port 8245 may be used to bypass transparent HTTP proxies. The update interface listens on ports for HTTP, and 443 for HTTPS. Hard coding the IP address is not acceptable as the IP address may change. Updates can be performed over HTTP or SSL-encrypted HTTPS (preferred).Īll requests should be sent to. If you have questions about the syntax, please contact Dyn support. Dyn will pass back a return code that the client needs to parse. All updates are sent using a well-formed HTTP request. When a change in IP address is found or a user alters any of their settings, the client should perform an update. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |