public inbox for ddns@lists.ipfire.org
 help / color / mirror / Atom feed
From: Jonas <jonas@desec.io>
To: ddns@lists.ipfire.org
Subject: Re: ddns patches for desec.io provider support
Date: Fri, 31 Jul 2015 01:51:21 +0200	[thread overview]
Message-ID: <55BAB879.5050300@desec.io> (raw)
In-Reply-To: <1438254010.2323.4.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]

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


  reply	other threads:[~2015-07-30 23:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 18:13 Jonas
2015-07-30 11:00 ` Michael Tremer
2015-07-30 23:51   ` Jonas [this message]
2015-07-31 10:09     ` Michael Tremer
2015-08-31 16:11       ` Jonas
2015-08-31 16:37         ` Michael Tremer
2015-09-01  8:10           ` Nils Wisiol
2015-10-08 19:56           ` Jonas
2015-10-15 11:08             ` Michael Tremer
2015-10-15 11:24               ` Stefan Schantl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55BAB879.5050300@desec.io \
    --to=jonas@desec.io \
    --cc=ddns@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox