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: Mon, 31 Aug 2015 18:11:17 +0200 Message-ID: <55E47CA5.6040804@desec.io> In-Reply-To: <1438337363.2356.9.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2234337087482456996==" List-Id: --===============2234337087482456996== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, sorry for the delay. The desec.io DDNS provider class is now implemented analog to http://git.ipfire.org/?p=ddns.git;a=blob;f=src/ddns/providers.py;h=6ac5 56444553fbf0d6e8b23854fe228ad6c81fc5;hb=HEAD#l805 for simultaneous IPv4/v6 updates as suggested by Michael. Registering IPv4 and IPv6 addresses with the update.dedyn.io server was successfully tested. Explicit unregistering will still require updates on the server side. Find attached the patches for src/ddns/providers.py and ddns.conf.sample -Jonas On 07/31/2015 12:09 PM, Michael Tremer wrote: > Hi, > > On Fri, 2015-07-31 at 01:51 +0200, Jonas wrote: >> 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) > That is actually a good idea to do, but that is not included in the > reference documentation of the DynDNS protocol. > > We have implemented this for an other provider so you can simply copy > those two lines and you are done: > > http://git.ipfire.org/?p=ddns.git;a=blob;f=src/ddns/providers.py;h=6ac5 > 56444553fbf0d6e8b23854fe228ad6c81fc5;hb=HEAD#l805 > >> As far as i understand the ddns sources, simultaneous >> updates are not possible. > They are. Just like the example above or this: > > http://git.ipfire.org/?p=ddns.git;a=blob;f=src/ddns/providers.py;h=6ac5 > 56444553fbf0d6e8b23854fe228ad6c81fc5;hb=HEAD#l1085 > > Most providers just require sending two requests which is not the most > preferable option, but what can you do?! > >> This may be resolved on the server side in the future. > What is probably quite important is to properly clear any IPv4 or IPv6 > addresses when a system does not have connectivity to either one any > more. > >> A possible workaround could be to always include >> both addresses in the update URL, independent of >> the "protocol" argument of the update method. > Will you send me an updated patch then? > > -Michael > >> 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 --===============2234337087482456996== Content-Type: text/x-patch Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="2015-08-31-ddns.conf.sample.diff" MIME-Version: 1.0 ZGlmZiAtLWdpdCBhL2RkbnMuY29uZi5zYW1wbGUgYi9kZG5zLmNvbmYuc2FtcGxlCmluZGV4IGJj NDIzMTkuLjMwNzdmOTAgMTAwNjQ0Ci0tLSBhL2RkbnMuY29uZi5zYW1wbGUKKysrIGIvZGRucy5j b25mLnNhbXBsZQpAQCAtNDMsNiArNDMsMTEgQEAKICMgdXNlcm5hbWUgPSB1c2VyCiAjIHBhc3N3 b3JkID0gcGFzcwogCisjIFt0ZXN0LmRlZHluLmlvXQorIyBwcm92aWRlciA9IGRlc2VjLmlvCisj IHVzZXJuYW1lID0gdXNlcgorIyBwYXNzd29yZCA9IHBhc3MKKwogIyBbdGVzdC5kaHMub3JnXQog IyBwcm92aWRlciA9IGRocy5vcmcKICMgdXNlcm5hbWUgPSB1c2VyCg== --===============2234337087482456996== Content-Type: text/x-patch Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="2015-08-31-providers.py.diff" MIME-Version: 1.0 ZGlmZiAtLWdpdCBhL3NyYy9kZG5zL3Byb3ZpZGVycy5weSBiL3NyYy9kZG5zL3Byb3ZpZGVycy5w eQppbmRleCA2YWM1NTY0Li4zODQ1MTkzIDEwMDY0NAotLS0gYS9zcmMvZGRucy9wcm92aWRlcnMu cHkKKysrIGIvc3JjL2RkbnMvcHJvdmlkZXJzLnB5CkBAIC01ODYsNiArNTg2LDMzIEBAIGNsYXNz IERETlNQcm92aWRlckNoYW5nZUlQKERETlNQcm92aWRlcik6CiAJCXJhaXNlIERETlNVcGRhdGVF cnJvcihfKCJTZXJ2ZXIgcmVzcG9uc2U6ICVzIikgJSBvdXRwdXQpCiAKIAorY2xhc3MgREROU1By b3ZpZGVyRGVzZWNJTyhERE5TUHJvdG9jb2xEeW5ETlMyLCBERE5TUHJvdmlkZXIpOgorCWhhbmRs ZSAgICA9ICJkZXNlYy5pbyIKKwluYW1lICAgICAgPSAiZGVzZWMuaW8iCisJd2Vic2l0ZSAgID0g Imh0dHBzOi8vd3d3LmRlc2VjLmlvIgorCXByb3RvY29scyA9ICgiaXB2NiIsICJpcHY0IiwpCisK KwkjIGlwdjQgLyBpcHY2IHJlY29yZHMgYXJlIGF1dG9tYXRpY2FsbHkgcmVtb3ZlZCB3aGVuIHRo ZSB1cGRhdGUKKwkjIHJlcXVlc3Qgb3JpZ2luYXRlcyBmcm9tIHRoZSByZXNwZWN0aXZlbHkgb3Ro ZXIgcHJvdG9jb2wgYW5kIG5vCisJIyBhZGRyZXNzIGlzIGV4cGxpY2l0bHkgcHJvdmlkZWQgZm9y IHRoZSB1bnVzZWQgcHJvdG9jb2wuCisKKwl1cmwgPSAiaHR0cHM6Ly91cGRhdGUuZGVkeW4uaW8i CisKKwkjIGRlc2VjLmlvIHNlbmRzIHRoZSBJUHY2IGFuZCBJUHY0IGFkZHJlc3MgaW4gb25lIHJl cXVlc3QKKworCWRlZiB1cGRhdGUoc2VsZik6CisJCWRhdGEgPSBERE5TUHJvdG9jb2xEeW5ETlMy LnByZXBhcmVfcmVxdWVzdF9kYXRhKHNlbGYsICJpcHY0IikKKworCQkjIFRoaXMgb25lIHN1cHBv cnRzIElQdjYKKwkJbXlpcHY2ID0gc2VsZi5nZXRfYWRkcmVzcygiaXB2NiIpCisKKwkJIyBBZGQg dXBkYXRlIGluZm9ybWF0aW9uIGlmIHdlIGhhdmUgYW4gSVB2NiBhZGRyZXNzLgorCQlpZiBteWlw djY6CisJCQlkYXRhWyJteWlwdjYiXSA9IG15aXB2NgorCisJCXNlbGYuc2VuZF9yZXF1ZXN0KGRh dGEpCisKKwogY2xhc3MgREROU1Byb3ZpZGVyREROU1MoREROU1Byb3ZpZGVyKToKIAloYW5kbGUg ICAgPSAiZGRuc3MuZGUiCiAJbmFtZSAgICAgID0gIkRETlNTIgo= --===============2234337087482456996==--