When a user sets up a service to be updated by DNS-O-Matic, they will be asked to provide their update password (if available), and encouraged strongly not to provide their service password unless no other alternative exists. Note on service passwords: Many dynamic DNS services have an update password, separate from the account password. Users will also enter a list of hostnames (FQDNs) to be updated. Dots, dashes, and underscores allowed, but not at the beginning or end of the string. DNS-O-Matic passwords are 6-20 characters. DNS-O-Matic usernames are 3-25 characters. URL Authentication: For web browsers or utilities (fetch, curl, lwp-request) which parse authentification section in need to enter a DNS-O-Matic username and password. An example would be: SoftwareDev - Fast Update Client - 2.0įailure to use a well-formed and consistent User-Agent string MAY result in failed update requests. Note: All clients must send a well-formed User-Agent including company name, model number, and software build revision. Update requests must be sent using HTTPS on port 443, Implementors MUST NOT hard code the IP for as they may change from time to time. When sending an update to be sure to always do a DNS query to resolve the IP for this host. DNS-O-Matic will pass back a return pre for the client 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. Example:įor clients using OpenDNS, a DNS request for '''' will always return the public IP of the client. Clients can determine the current public IP via the operating system's network stack or via web detection, useful for private IPs (RFC 1918 space).ĭNS-O-Matic operates a web service for detecting the user's public IP, available to clients that work with DNS-O-Matic.Īn HTTP request to will return the public IP of the client. DNS-O-Matic propagates update across all user subscribed services.Ī client must know its current public IP address and trigger updates when necessary.Client software sends an update request to DNS-O-Matic.Client software initializes or detects a change in the client IP adddress.Questions or feedback? familiar with the DynDNS Remote Access Update API will find the DNS-O-Matic API similar.Version: 0.9 (When the API reaches version 1.0, all future changes will be backwards compatible.).The API should be used by all client developers (software or hardware) who need to distribute IP address updates to dynamic DNS services. The DNS-O-Matic API enables that service for client developers. DNS-O-Matic gives dynamic IP address users a simple way to distribute their IP changes to multiple services with a single update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |