public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: DDNS: add new Provider key-sytems.net (domaindiscount24)
Date: Thu, 28 Nov 2019 11:20:49 +0000	[thread overview]
Message-ID: <4143661B-9526-49CE-AECD-7FD2E03D0DF7@ipfire.org> (raw)
In-Reply-To: <81dc1ed3-1179-42c6-784a-15f64a79508c@gmx.at>

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

Hello Christof,

> On 28 Nov 2019, at 10:45, Christof Weniger <ChristofWeniger(a)gmx.at> wrote:
> 
> Hi,
> 
> I hope this is the correct way to submit this patch.

Yes, you found the right place.

It would have been better to post the patch inline (and not as an attachment), so that I could have commented on it.

> https://www.domaindiscount24.com/ has its own ddns service runnning,
> which (for me) gets rid of the necessity of having to use an extra
> service for that.
> 
> I tested the following patch on my system at home, and attached it to
> this mail.
> 
> I started my quest at the community forum:
> https://community.ipfire.org/t/adding-new-ddns-provider/428/2
> 
> Christof
> 
> 
> 
> 
> 
> <add_key_systems_ddns.patch>

I will make an exception here now and still give you my thoughts :)

It looks like this is very close to the DynDNS protocol, so you can re-use that as some other providers do.

Unfortunately this provider has no list of any possible responses - or maybe I have overlooked it. That can however be tested to check if those are still compatible with DynDNS.

Finally, you are setting the IP addresses to “auto” which probably is not a good idea. I would prefer that it is explicitly being set. There is a function for it that finds out which one is the correct IP address.

In the end I think this provider could look like “myonlineportal”: https://git.ipfire.org/?p=ddns.git;a=blob;f=src/ddns/providers.py;h=661fbcc57a5aecba0d958ec05c26296b3cef0d70;hb=HEAD#l1274

Best,
-Michael

  reply	other threads:[~2019-11-28 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 10:45 Christof Weniger
2019-11-28 11:20 ` Michael Tremer [this message]
     [not found] <23d7d16f-1098-13d0-152a-651c4ff6d50a@gmx.at>
2019-11-28 13:35 ` Michael Tremer
     [not found] <97e435c3-36ba-0468-34a4-68081f4c4520@gmx.at>
2019-11-28 15:17 ` Michael Tremer

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=4143661B-9526-49CE-AECD-7FD2E03D0DF7@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@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