From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: ddns@lists.ipfire.org
Subject: Re: ddns patches for desec.io provider support
Date: Fri, 31 Jul 2015 11:09:23 +0100
Message-ID: <1438337363.2356.9.camel@ipfire.org>
In-Reply-To: <55BAB879.5050300@desec.io>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3377788362421362968=="
List-Id: <ddns.lists.ipfire.org>

--===============3377788362421362968==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

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
> 

--===============3377788362421362968==
Content-Type: application/pgp-signature
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="signature.asc"
MIME-Version: 1.0

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjEKCmlRSWNCQUFC
Q2dBR0JRSlZ1MGxUQUFvSkVJQjU4UDl2a0FrSFVzMFAvM09sNCs5N1doYU92eGN1bDZjSytGSTQK
cG5HcUhpelF2Sy8yY2tQc0RJT2FGQzJBNHpjeU9vNkdZL2IzTGFFTEs1UndGeFY5cDl4TXVYbkZ6
L0s5QXpZaApITnd0VFVYQmVVQkZQV2tsQVg2czJQZ28rR250UUNwcUJaTXdNc3RjV0I5NnBEbCt4
U2hSRjJ3cVdKbS8xQmxjCjVKRVdMcWQxdHBVaEg2VmJ3dFJSdE9obm9nRTVTSUJZankzbkU4eHZB
MW1yMXgyWFI5SExQMllYTnArUTF6WHEKWG5GdGxDd1kyTnhRcEd5MEIvYldTVHBjWFoyZllHT1dS
SC9pTVIvaFlKQ1F5ZktkQ1pmWndFRmx0RzdmSzZQTgpUTGYzV0t2ZTVtZmpPdWRlUGhScjN2M3Nq
ZEVlaFJOa0lHMkxFUlFMeThVbVBGYXgwQjJ0RnBNTWVhOXhTT3o4CmdvOG1ETlJsbnVCTTQyQThE
MGVVdHExTmp6L2dlb2V3Ui9UWmtoTmNPNUtpeU9GZnhtS1F3UEJ2NS9WQnZaNVkKalF5MEdiSGRY
VW5lbFBUN2VrUkh2Y0ZHYmZSYzhPU3JnYW9FT0cwTE01S2JkOXp0SXRFczFlTXJSYUN0SFVxdQpz
elNTK3BlNDlSZ1FsZ1YxMnpIeG54cHQ4RHFlN21aZTFwZmgyZWVhSlQ0Tm13Tk43Z1JxcE43eDZP
Y2JIU25DCnpKVGtUK0t0Q2lWcG5nSjFINzkwcnhPZ0FsZEFBOWc4QWU0OE1QMXVBbUJ1OXhVMEQ0
c2pCZG1iRzRWdW9UUEYKK00raWd3UmlFbWRCNW5GUExEQkUvakZyOWdlTm9OL0pkd244Rno0SXBh
aTZERnh6RHB1bFBqTXkxZmFrZ0drUwphUnpFN0JPRS8zVkExUThzYXVKNAo9M0d1cAotLS0tLUVO
RCBQR1AgU0lHTkFUVVJFLS0tLS0K

--===============3377788362421362968==--