make webcheck url configurable per service about python-dyndnsc HOT 6 CLOSED

a) I agree, it's confusing. Which URL do you suggest making the "it-just-works" default for ipv4/ipv6?

b) webcheck4, webcheck46 and webcheck6 exist respectively, so I'm not sure what you mean

c) ?

from python-dyndnsc.

a) it's not about having a "it-just-works" default (same for all services), it is about using the specific webcheck url of the specific service one uses.

b) yes, i found webcheck6 later.

c) even after giving the webcheck6, it is still somehow confused and compares v4 to v6... - guess it gets the v4 from dns and compares it to the v6 from webcheck6 or interface.

from python-dyndnsc.

a slight improvement for this is pull request #23 which makes url and parser user configurable (cmdline options), so at least users can prevent dyndnsc from querying random and sometimes non-working services. also, the user can give a https url.

from python-dyndnsc.

I looked a bit more into this to see if the PR can be improved more, but I think with the current way how dyndnsc deals with stuff, this is not possible, so the PR is maybe as good as it gets.

dyndnsc seems to have no concept of a service definition (that would contain checkip url(s), update url(s), infos whether tls is possible, whether v4 and/or v6 are supported). because of that, checkers and updaters live an independent life and are just coupled together via the cmdline options.

from python-dyndnsc.

c) is fixed by PR #26

from python-dyndnsc.

created new issue #28 for service definitions

from python-dyndnsc.