Register a Domain: .biz.bz.ca.cc.cn.com.info.mobi.net.nu.org.sh.tv.ws
	·     ·  Home   ·  New Account   ·  Admin Section   ·  Help

yi.org Help: Technical Info: Protocols

As well as the web-based administration section (which is served using HTTP), there are three protocols that may be used to update your IP address in yi.org's DNS database. The preferred protocol is GnuDIP2.

NOTE: These protocols will only update "A" records on your hosts that have been marked as "Primary". In the future, there will be a method to have finer-grain control over your DNS tables by dynamic update. If your updates are showing up as successful, but your IP isn't being updated, make sure you have an "A" record in the appropriate namespace and that at least one "A" record has been set as "Primary"!

• GnuDIP2
• MonoLith (ml.org)
• WeeDNS v1

GnuDIP2 is by far the best protocol to use when updating your yi.org IP. It has very little overhead and never transmits passwords in plaintext. A comprehensive description of this protocol can be found at http://gnudip2.sourceforge.net/gnudip-www/latest/gnudip/html/protocol.html.

yi.org supports both the TCP and HTTP methods of GnuDIP2 update. TCP is the preferred method. Here are the settings for both:

ml.org was the very first public Dynamic DNS service on the Internet. It stayed up for a few years and worked well most of the time. The original nx.org (later renamed to yi.org) service emulated this protocol in order to support Dynamic DNS clients that had already been written for MonoLith's services.

The protocol is extremely simple:

1. Send a HTTP GET request to http://www.yi.org/bin/dyndns.fcgi.
   • Use "Basic" HTTP Authorization with the username set to the full name of the host you wish to update ("hostname.yi.org") and the password set to your yi.org account's password.
   • If you wish to specify an IP address instead of it being automatically detected, specify it as the ipaddr parameter in the query. For instance, "http://www.yi.org/bin/dyndns.fcgi?ipaddr=11.22.33.44".
2. The server will send back a response. If the string "STATUS:OK" is in the response, then the update was successful. Here is an example document that might be sent from the yi.org server for a successful update:

   1[update] update results follow.
   1[a(hostname.yi.org)] 1 11.22.33.44
   <!-- MS3V STATUS:OK HOSTNAME:a(hostname.yi.org)=11.22.33.44 ACT:1 IP: MX:na -->
   Your request has been processed successfully.

   If "STATUS:OK" is not found within the document, an error occured.

With the MonoLith protocol it is possible to use just about any web browser to preform a quick update. However, it has more overhead than GnuDIP2 and it does not transmit passwords securely. If you are going to use any client software at all to update your IP, I strongly suggest you use the GnuDIP2 update method instead.

This protocol is completely depreciated. It is only supported right now to prevent hosts that are still set up to use it from breaking. Use GnuDIP2 instead.

Not all portions of the WeeDNS protocol are supported in this version. The capibilities have been stripped down to what is neccessary to keep hosts active that haven't upgraded yet - logging in and making IP updates via the "a()" action.

With that in mind, you can read all about the old protocol here.

Apache/2.2.9 (Debian) mod_ssl/2.2.9 OpenSSL/0.9.8g mod_perl/2.0.4 Perl/v5.10.0 Server at www.yi.org Port 80