From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonas To: ddns@lists.ipfire.org Subject: Re: ddns patches for desec.io provider support Date: Fri, 31 Jul 2015 01:51:21 +0200 Message-ID: <55BAB879.5050300@desec.io> In-Reply-To: <1438254010.2323.4.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1998162994397167482==" List-Id: --===============1998162994397167482== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hello Michael, in case of both IPv4 and IPv6 connection, the query string in the update URL may contain both a "myip" and a "myipv6" key simultaneously. (for single protocol updates, "myip" may be used for either protocol) As far as i understand the ddns sources, simultaneous updates are not possible. This may be resolved on the server side in the future. A possible workaround could be to always include both addresses in the update URL, independent of the "protocol" argument of the update method. Kind regards, Jonas On 07/30/2015 01:00 PM, Michael Tremer wrote: > Hello Jonas, > > thank you very much for sending in this patch. It looks really good. > > I was just wondering if it wouldn't be better to implement IPv6 support > properly. As far as I understand it, ddns will send two updates and the > second one will delete the updated data from the first one. In case of > a system having connectivity to the IPv6 and IPv4 Internet, the DNS > record will just point to the IPv4 address. Correct me if I am wrong > here. Now it only works if a system has either IPv6 or IPv4 > connectivity. > > Let me know if we can solve this problem. > > Best, > -Michael > > > On Wed, 2015-07-29 at 20:13 +0200, Jonas wrote: >> Hi, >> >> >> i'd like to add support for the desec.io >> dyndns service. >> >> It is DynDNS 2 compatible, so the patch is small. >> >> >> >> Regards, >> Jonas --===============1998162994397167482==--