ddclient-support — Support for ddclient

Re: [Ddclient-support] Project ownership

[wimpunk <wi...@us...>]

On 8/20/19 5:48 PM, Dave Smith wrote:
> Can you add me as a member of the GitHub?
> 
> My username is DaveSophoServices
> 
> Dave.
> 

Dave,

You've sent this mail from another email address than the one you used
to register on the list.  Therefore the mail didn't reached the mailing
list.  Oh, and please, can you reply at the bottom of the messages on
the mailing list?  It makes reading more easily.

I've add you as a member.  After you accept this, I can give you more
rights than you currently do.
Thanks again for helping me out with this.

Kind regards,

wimpunk.

Re: [Ddclient-support] Project ownership

[wimpunk <wi...@us...>]

On 8/20/19 3:07 AM, Dave Smith wrote:
> Are you guys still looking for someone to help maintain this project?
> 
> I'm willing to help, or do what's needed.
> 
> Dave
> 
> 

There is no such thing as guys, it's mostly me who's working on this.
I'm trying to move everything to gitlab (see
https://github.com/ddclient) and it would be great if some people could
help me to maintain the project.

I have no list on what has to be done but it would be great of you could
help.
First step would be to review the issues on github.  We also have to
update the documentation and fix indentation of the script.

Kind regards,

wimpunk.

[Ddclient-support] Project ownership

[Dave S. <sf...@so...>]

Are you guys still looking for someone to help maintain this project?

I'm willing to help, or do what's needed.

Dave

[Ddclient-support] [ddclient/ddclient] e910af: Restore ability to update multiple namecheap domai...

[Ian C. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/ddclient/ddclient
  Commit: e910af8bac4b11312577c4b46b3e96807cc64f84
      https://github.com/ddclient/ddclient/commit/e910af8bac4b11312577c4b46b3e96807cc64f84
  Author: Ian Colwell <ico...@gs...>
  Date:   2019-06-06 (Thu, 06 Jun 2019)

  Changed paths:
    M ddclient
    M sample-etc_ddclient.conf

  Log Message:
  -----------
  Restore ability to update multiple namecheap domains (#64)

* Revert to previous functionality
* Revert example config
* Remove redundant commas
* Update example conf
* Revert whitespace formatting

[Ddclient-support] Taking the project ownership

[<wi...@us...>]

Hi,

Is there anyone on this list willing to take the ownership of the project?  I don't have enough time to work on ddclient so maybe some else out here want to take the ownership.

Kind regards,

wimpunk.

Re: [Ddclient-support] clouflare dns no longer working

[Ellie R. <ell...@gm...>]

Hi,
while doing that pastebin I noticed something was very very wrong with 
this thing. I have absolutely no idea as to why, but it appears that 
cloudflare protocol was accidentally set to use ipv4.tunnelbroker.net -- 
that won't do at all !

As I understood it I could define another config section for another 
protocol... It appears that since I didn,t set any server in the 
cloudflare protocol section of my config file, that the 
ipv4.tunnelbroker.net of my tunnelbroker section, complete with dyndns2, 
is overriding the default cloudflare server entirely....
Should this be expected ?

Should I manually set the cloudflare server in this case and if so to 
what exactly ?
Thanks

wi...@us... a écrit :
>
>> On 11 Dec 2018, at 12:45, Ellie Revves <ell...@gm...> wrote:
>>
>> Hi,
>> subject pretty much says it all
>> I cannot seem to get the cloudflare protocol to work anymore even though I have not changed my config, I only have this as output to debug:
>>
>> WARNING:  file /var/cache/ddclient/ddclient.cache, line 4: Invalid Value for keyword 'ip' = ''
>> WARNING:  skipping update of mydomain.com from <nothing> to xx.xx.xxx.xx.
>> WARNING:   last updated <never> but last attempt on Tue Dec 11 08:31:29 2018 failed.
>>
>> And this line in the ddclient cache:
>>
>> atime=1544517689,backupmx=0,host=mydomain.com,ip=,mtime=0,mx=,static=0,status=noconnect,warned-min-error-interval=0,warned-min-interval=0,wildcard=0,wtime=0 mydomain.com
>>
>> I have not touched anything except the config options I needed in the ddclient.conf:
>>
>> use=if,                     if=wan              # via interfaces
>> ssl=yes                                 # use ssl-support.  Works with
>> daemon=300                              # check every 300 seconds
>> syslog=yes                              # log update msgs to syslog
>> pid=/var/run/ddclient.pid               # record PID in file.
>> ## CloudFlare (www.cloudflare.com)
>> protocol=cloudflare,        \
>> zone=mydomain.com,                 \
>> login=my_email, \
>> password=my_token, \
>> mydomain.com,
>>
>> Can anyone help out ? I also update my tunnelbroker ip with the exact same config at least for ssl and using the wan interface -- the interface IS really called wan.
>> Thanks !
>>
>>
> Can you please run ddclient -daemon=0 -debug -verbose -noquiet  and post the result on pastebin?
>
> Kind regards,
>
> wimpunk.
>

Re: [Ddclient-support] clouflare dns no longer working

[<wi...@us...>]

> On 11 Dec 2018, at 12:45, Ellie Revves <ell...@gm...> wrote:
> 
> Hi,
> subject pretty much says it all
> I cannot seem to get the cloudflare protocol to work anymore even though I have not changed my config, I only have this as output to debug:
> 
> WARNING:  file /var/cache/ddclient/ddclient.cache, line 4: Invalid Value for keyword 'ip' = ''
> WARNING:  skipping update of mydomain.com from <nothing> to xx.xx.xxx.xx.
> WARNING:   last updated <never> but last attempt on Tue Dec 11 08:31:29 2018 failed.
> 
> And this line in the ddclient cache:
> 
> atime=1544517689,backupmx=0,host=mydomain.com,ip=,mtime=0,mx=,static=0,status=noconnect,warned-min-error-interval=0,warned-min-interval=0,wildcard=0,wtime=0 mydomain.com
> 
> I have not touched anything except the config options I needed in the ddclient.conf:
> 
> use=if,                     if=wan              # via interfaces
> ssl=yes                                 # use ssl-support.  Works with
> daemon=300                              # check every 300 seconds
> syslog=yes                              # log update msgs to syslog
> pid=/var/run/ddclient.pid               # record PID in file.
> ## CloudFlare (www.cloudflare.com)
> protocol=cloudflare,        \
> zone=mydomain.com,                 \
> login=my_email, \
> password=my_token, \
> mydomain.com,
> 
> Can anyone help out ? I also update my tunnelbroker ip with the exact same config at least for ssl and using the wan interface -- the interface IS really called wan.
> Thanks !
> 
> 

Can you please run ddclient -daemon=0 -debug -verbose -noquiet  and post the result on pastebin?

Kind regards,

wimpunk.

[Ddclient-support] clouflare dns no longer working

[Ellie R. <ell...@gm...>]

Hi,
subject pretty much says it all
I cannot seem to get the cloudflare protocol to work anymore even though 
I have not changed my config, I only have this as output to debug:

WARNING:  file /var/cache/ddclient/ddclient.cache, line 4: Invalid Value 
for keyword 'ip' = ''
WARNING:  skipping update of mydomain.com from <nothing> to xx.xx.xxx.xx.
WARNING:   last updated <never> but last attempt on Tue Dec 11 08:31:29 
2018 failed.

And this line in the ddclient cache:

atime=1544517689,backupmx=0,host=mydomain.com,ip=,mtime=0,mx=,static=0,status=noconnect,warned-min-error-interval=0,warned-min-interval=0,wildcard=0,wtime=0 
mydomain.com

I have not touched anything except the config options I needed in the 
ddclient.conf:

use=if,                     if=wan              # via interfaces
ssl=yes                                 # use ssl-support.  Works with
daemon=300                              # check every 300 seconds
syslog=yes                              # log update msgs to syslog
pid=/var/run/ddclient.pid               # record PID in file.
## CloudFlare (www.cloudflare.com)
protocol=cloudflare,        \
zone=mydomain.com,                 \
login=my_email, \
password=my_token, \
mydomain.com,

Can anyone help out ? I also update my tunnelbroker ip with the exact 
same config at least for ssl and using the wan interface -- the 
interface IS really called wan.
Thanks !

Re: [Ddclient-support] secure updates not working with DynDNS - debian stretch

[<wi...@us...>]

Can you post the output of the two commands on pastebin?  They should both use ssl so I'm a bit surprised there's a difference between them.

Kind regards,

wimpunk.

> On 11 Dec 2018, at 09:34, Juan Alonso <sc...@gm...> wrote:
> 
> Ok, I did not understand. I switched the two mentioned lines and if I try to update like this:
> 
> sudo ddclient -daemon=0 -debug -verbose -noquiet -force
> 
> it says that is updating via SSL. 
> 
> But if I try this (not forcing the update):
> 
> sudo ddclient -daemon=0 -debug -verbose -noquiet
> 
> it says that is updating via HTTP.
> 
> 
> For security, I have generated Updater Client Key in DynDNS to avoid using user password.
> 
> But, is there any way to see if updatings are via SSL? ddclient.cache file does not store information about that.
> 
> /var/cache/ddclient/ddclient.cache 
> 
> ## ddclient-3.8.3
> ## last updated at Tue Dec 11 09:23:10 2018 (1544516590)
> atime=0,backupmx=0,custom=0,host=mydomain.dyndns.org <http://mydomain.dyndns.org/>,ip=myip,mtime=1544516578,mx=,script=/nic/update,static=0,status=good,warned-min-error-interval=0,warned-min-interval=0,wildcard=0,wtime=30 mydomain.dyndns.org <http://mydomain.dyndns.org/>
> 
> thanks a lot!
> 
> 
> El mié., 5 dic. 2018 a las 9:42, wimpunk--- via Ddclient-support (<ddc...@li... <mailto:ddc...@li...>>) escribió:
> Hi,
> 
> > On 4 Dec 2018, at 20:17, Juan Alonso <sc...@gm... <mailto:sc...@gm...>> wrote:
> > 
> > Hi,
> > 
> > I'm not able to make updates via SSL. ddclient is working, but with http
> > updates.
> > 
> > I'm using Debian Stretch and I have installed ddclient from repositories.
> > I have also installed libio-socket-ssl-perl
> > 
> > However I tried Ubuntu 16.04 too and the same happened.
> > 
> > *Some logs:*
> > 
> > The next command tells me "CONNECTED: using HTTP"
> > 
> > sudo ddclient -daemon=0 -debug -verbose -noquiet
> > 
> > 
> > This is ddclient.conf
> > 
> > pid=/var/run/ddclient.pid
> > ssl=yes
> > protocol=dyndns2
> > use=web, web=checkip.dyndns.com <http://checkip.dyndns.com/>, web-skip='IP Address'
> > server=members.dyndns.org <http://members.dyndns.org/>
> > login=myuser
> > password='mypassword'
> > mydomain.dyndns.org <http://mydomain.dyndns.org/>
> > 
> 
> 
> Can you switch the protocol and the use line?  That should fix your problem.
> 
> Kind regards,
> 
> wimpunk.
> 
> 
> _______________________________________________
> Ddclient-support mailing list
> Ddc...@li... <mailto:Ddc...@li...>
> https://lists.sourceforge.net/lists/listinfo/ddclient-support <https://lists.sourceforge.net/lists/listinfo/ddclient-support>
> 
> 
> -- 
> 
> Juan José Alonso
> 
> www.avlaunionfuencarral.org <http://www.avlaunionfuencarral.org/>
> windowsclosed.blogspot.com.es <http://windowsclosed.blogspot.com.es/>

Re: [Ddclient-support] secure updates not working with DynDNS - debian stretch

[Juan A. <sc...@gm...>]

Ok, I did not understand. I switched the two mentioned lines and if I try
to update like this:

sudo ddclient -daemon=0 -debug -verbose -noquiet -force

it says that is updating via SSL.

But if I try this (not forcing the update):

sudo ddclient -daemon=0 -debug -verbose -noquiet

it says that is updating via HTTP.


For security, I have generated *Updater Client Key* in DynDNS to avoid
using user password.

But, is there any way to see if updatings are via SSL? ddclient.cache file
does not store information about that.

/var/cache/ddclient/ddclient.cache

## ddclient-3.8.3
## last updated at Tue Dec 11 09:23:10 2018 (1544516590)
atime=0,backupmx=0,custom=0,host=mydomain.dyndns.org,ip=myip,mtime=1544516578,mx=,script=/nic/update,static=0,status=good,warned-min-error-interval=0,warned-min-interval=0,wildcard=0,wtime=30
mydomain.dyndns.org

thanks a lot!


El mié., 5 dic. 2018 a las 9:42, wimpunk--- via Ddclient-support (<
ddc...@li...>) escribió:

> Hi,
>
> > On 4 Dec 2018, at 20:17, Juan Alonso <sc...@gm...> wrote:
> >
> > Hi,
> >
> > I'm not able to make updates via SSL. ddclient is working, but with http
> > updates.
> >
> > I'm using Debian Stretch and I have installed ddclient from repositories.
> > I have also installed libio-socket-ssl-perl
> >
> > However I tried Ubuntu 16.04 too and the same happened.
> >
> > *Some logs:*
> >
> > The next command tells me "CONNECTED: using HTTP"
> >
> > sudo ddclient -daemon=0 -debug -verbose -noquiet
> >
> >
> > This is ddclient.conf
> >
> > pid=/var/run/ddclient.pid
> > ssl=yes
> > protocol=dyndns2
> > use=web, web=checkip.dyndns.com, web-skip='IP Address'
> > server=members.dyndns.org
> > login=myuser
> > password='mypassword'
> > mydomain.dyndns.org
> >
>
>
> Can you switch the protocol and the use line?  That should fix your
> problem.
>
> Kind regards,
>
> wimpunk.
>
>
> _______________________________________________
> Ddclient-support mailing list
> Ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddclient-support
>


-- 

Juan José Alonso

www.avlaunionfuencarral.org
windowsclosed.blogspot.com.es

Re: [Ddclient-support] secure updates not working with DynDNS - debian stretch

[<wi...@us...>]

Hi,

Please continue using the mailing list, don't mail me directly.

> On 5 Dec 2018, at 20:28, Juan Alonso <sc...@gm...> wrote:
> 
> I am using dyndns, so I think I cannot use another protocol. And use line is working ok because IP is updated fine, but via HTTP.
> 
> Anyway, can you suggest me other configuration for that two lines, in order updates become working via HTTPS?
> 
> thanks a lot!


I think you just misunderstood me. You don't have to change the lines, you just have to switch the order of the lines.  That way ssl=yes will apply to the dyndns-protocol.  If you switch those two lines, you'll see that ssl will be set when running in debug mode.

Kind regards,

wimpunk.

Re: [Ddclient-support] secure updates not working with DynDNS - debian stretch

[<wi...@us...>]

Hi,

> On 4 Dec 2018, at 20:17, Juan Alonso <sc...@gm...> wrote:
> 
> Hi,
> 
> I'm not able to make updates via SSL. ddclient is working, but with http
> updates.
> 
> I'm using Debian Stretch and I have installed ddclient from repositories.
> I have also installed libio-socket-ssl-perl
> 
> However I tried Ubuntu 16.04 too and the same happened.
> 
> *Some logs:*
> 
> The next command tells me "CONNECTED: using HTTP"
> 
> sudo ddclient -daemon=0 -debug -verbose -noquiet
> 
> 
> This is ddclient.conf
> 
> pid=/var/run/ddclient.pid
> ssl=yes
> protocol=dyndns2
> use=web, web=checkip.dyndns.com, web-skip='IP Address'
> server=members.dyndns.org
> login=myuser
> password='mypassword'
> mydomain.dyndns.org
> 


Can you switch the protocol and the use line?  That should fix your problem.

Kind regards,

wimpunk.

[Ddclient-support] secure updates not working with DynDNS - debian stretch

[Juan A. <sc...@gm...>]

Hi,

I'm not able to make updates via SSL. ddclient is working, but with http
updates.

I'm using Debian Stretch and I have installed ddclient from repositories.
I have also installed libio-socket-ssl-perl

However I tried Ubuntu 16.04 too and the same happened.

*Some logs:*

The next command tells me "CONNECTED: using HTTP"

sudo ddclient -daemon=0 -debug -verbose -noquiet


This is ddclient.conf

pid=/var/run/ddclient.pid
ssl=yes
protocol=dyndns2
use=web, web=checkip.dyndns.com, web-skip='IP Address'
server=members.dyndns.org
login=myuser
password='mypassword'
mydomain.dyndns.org


/var/cache/ddclient/ddclient.cache

## ddclient-3.8.3
## last updated at Mon Dec  3 11:32:43 2018 (1543833163)
atime=0,backupmx=0,custom=0,host=mydomain.dyndns.org
,ip=my.public.ip.here,mtime=1543703401,mx=,script=/nic/update,static=0,status=,warned-min-error-interval=0,warned-min-interval=0,wildcard=0,wtime=30
mydomain.dyndns.org


sudo ddclient -daemon=0 -debug -verbose -noquiet


=== opt ====
opt{cache}                           : <undefined>
opt{cmd}                             : <undefined>
opt{cmd-skip}                        : <undefined>
opt{daemon}                          : 0
opt{debug}                           : 1
opt{exec}                            : <undefined>
opt{facility}                        : <undefined>
opt{file}                            : <undefined>
opt{force}                           : <undefined>
opt{foreground}                      : <undefined>
opt{fw}                              : <undefined>
opt{fw-login}                        : <undefined>
opt{fw-password}                     : <undefined>
opt{fw-skip}                         : <undefined>
opt{geturl}                          : <undefined>
opt{help}                            : <undefined>
opt{host}                            : <undefined>
opt{if}                              : <undefined>
opt{if-skip}                         : <undefined>
opt{ip}                              : <undefined>
opt{login}                           : <undefined>
opt{mail}                            : <undefined>
opt{mail-failure}                    : <undefined>
opt{max-interval}                    : 2592000
opt{min-error-interval}              : 300
opt{min-interval}                    : 30
opt{options}                         : <undefined>
opt{password}                        : <undefined>
opt{pid}                             : <undefined>
opt{postscript}                      : <undefined>
opt{priority}                        : <undefined>
opt{protocol}                        : <undefined>
opt{proxy}                           : <undefined>
opt{query}                           : <undefined>
opt{quiet}                           : 0
opt{retry}                           : <undefined>
opt{server}                          : <undefined>
opt{ssl}                             : <undefined>
opt{syslog}                          : <undefined>
opt{test}                            : <undefined>
opt{timeout}                         : <undefined>
opt{use}                             : <undefined>
opt{usev6}                           : <undefined>
opt{verbose}                         : 1
opt{web}                             : <undefined>
opt{web-skip}                        : <undefined>
=== globals ====
globals{daemon}                      : 60
globals{debug}                       : 1
globals{login}                       : myuser
globals{password}                    : mypassword
globals{pid}                         : /var/run/ddclient.pid
globals{protocol}                    : dyndns2
globals{quiet}                       : 0
globals{server}                      : members.dyndns.org
globals{ssl}                         : 1
globals{use}                         : web
globals{verbose}                     : 1
globals{web}                         : checkip.dyndns.com
globals{web-skip}                    : IP Address
=== config ====
config{mydomain.dyndns.org}{atime} : 0
config{mydomain.dyndns.org}{backupmx} : 0
config{mydomain.dyndns.org}{cacheable} : ARRAY(0x55f4b2a2eb70)
config{mydomain.dyndns.org}{cmd} : <undefined>
config{mydomain.dyndns.org}{cmd-skip} :
config{mydomain.dyndns.org}{custom} : 0
config{mydomain.dyndns.org}{fw} :
config{mydomain.dyndns.org}{fw-login} : <undefined>
config{mydomain.dyndns.org}{fw-password} :
config{mydomain.dyndns.org}{fw-skip} :
config{mydomain.dyndns.org}{host} : mydomain.dyndns.org
config{mydomain.dyndns.org}{if} : ppp0
config{mydomain.dyndns.org}{if-skip} :
config{mydomain.dyndns.org}{ip} : <undefined>
config{mydomain.dyndns.org}{login} : myuser
config{mydomain.dyndns.org}{max-interval} : 2592000
config{mydomain.dyndns.org}{min-error-interval} : 300
config{mydomain.dyndns.org}{min-interval} : 30
config{mydomain.dyndns.org}{mtime} : 0
config{mydomain.dyndns.org}{mx} :
config{mydomain.dyndns.org}{password} : mypassword
config{mydomain.dyndns.org}{protocol} : dyndns2
config{mydomain.dyndns.org}{script} : /nic/update
config{mydomain.dyndns.org}{server} : members.dyndns.org
config{mydomain.dyndns.org}{static} : 0
config{mydomain.dyndns.org}{status} :
config{mydomain.dyndns.org}{use} : web
config{mydomain.dyndns.org}{usev6} : <undefined>
config{mydomain.dyndns.org}{warned-min-error-interval} : 0
config{mydomain.dyndns.org}{warned-min-interval} : 0
config{mydomain.dyndns.org}{web} : checkip.dyndns.com
config{mydomain.dyndns.org}{web-skip} : IP Address
config{mydomain.dyndns.org}{wildcard} : 0
config{mydomain.dyndns.org}{wtime} : 30
=== cache ====
cache{mydomain.dyndns.org}{atime} : 0
cache{mydomain.dyndns.org}{backupmx} : 0
cache{mydomain.dyndns.org}{custom} : 0
cache{mydomain.dyndns.org}{host} : mydomain.dyndns.org
cache{mydomain.dyndns.org}{ip} : my.public.ip.here
cache{mydomain.dyndns.org}{mtime} : 1543703401
cache{mydomain.dyndns.org}{mx} :
cache{mydomain.dyndns.org}{script} : /nic/update
cache{mydomain.dyndns.org}{static} : 0
cache{mydomain.dyndns.org}{status} :
cache{mydomain.dyndns.org}{warned-min-error-interval} : 0
cache{mydomain.dyndns.org}{warned-min-interval} : 0
cache{mydomain.dyndns.org}{wildcard} : 0
cache{mydomain.dyndns.org}{wtime} : 30
DEBUG:    proxy  =
DEBUG:    url    = checkip.dyndns.com
DEBUG:    server = checkip.dyndns.com
CONNECT:  checkip.dyndns.com
CONNECTED:  using HTTP
SENDING:  GET / HTTP/1.0
SENDING:   Host: checkip.dyndns.com
SENDING:   User-Agent: ddclient/3.8.3
SENDING:   Connection: close
SENDING:
RECEIVE:  HTTP/1.1 200 OK
RECEIVE:  Content-Type: text/html
RECEIVE:  Server: DynDNS-CheckIP/1.0.1
RECEIVE:  Connection: close
RECEIVE:  Cache-Control: no-cache
RECEIVE:  Pragma: no-cache
RECEIVE:  Content-Length: 105
RECEIVE:
RECEIVE:  <html><head><title>Current IP Check</title></head><body>Current
IP Address: my.public.ip.here</body></html>
DEBUG:    get_ip: using web, checkip.dyndns.com reports my.public.ip.here
SUCCESS:  mydomain.dyndns.org: skipped: IP address was already set to
my.public.ip.here.

I followed this instructions:
https://help.dyn.com/ddclient/


Any help please?
Thanks in advance

Juanjo

Re: [Ddclient-support] ddclient updates not working -- invalid logins

[wimpunk <wi...@us...>]

Great to know it worked. :-)

Kind regards,

Wim.

On 10/9/18 7:54 AM, Mark Adams wrote:
> Okay. Well, that was easy.
> 
> Thanks much Wim!
> 
> Mark
> 
> On Mon, Oct 8, 2018 at 8:37 AM wimpunk via Ddclient-support
> <ddc...@li...
> <mailto:ddc...@li...>> wrote:
> 
> 
> 
>     On 10/5/18 1:57 AM, Mark Adams wrote:
>     > Greetings!
>     >
>     > Around the end of July my automatic ddns updates stopped working. My
>     > domain is registered at namecheap.com <http://namecheap.com> and I
>     was on chat with them for a
>     > couple of hours before they finally told me that they can't help
>     me and
>     > provided a link to information about manually updating my ddns. I find
>     > that a bit unsatisfying and am considering moving my registrar but I
>     > wanted to see if I could get this sorted out first.
>     >
>     > The trouble is in here somewhere. This is the output from "ddclient
>     > --force" on my server:
>     >
>     > # ddclient -force
>     > WARNING:  skipping host: @: 'login=' is an invalid login.
>     > WARNING:  skipping host: @: 'login=' is an invalid login.
>     > WARNING:  SENT:
>     >
>     http://dynamicdns.park-your-domain.com/update?host=\updated&domain=to&password=below&ip=64.130.86.93
>     <http://dynamicdns.park-your-domain.com/update?host=%5Cupdated&domain=to&password=below&ip=64.130.86.93>
>     >
>     > WARNING:  REPLIED: HTTP/1.1 200 OK
>     > WARNING:   Cache-Control: private
>     > WARNING:   Content-Type: text/html
>     > WARNING:   Set-Cookie: ASPSESSIONIDSQTCDSAT=KEDDLBADPKAMKAMMIDKCCODF;
>     > path=/
>     > WARNING:   Date: Thu, 04 Oct 2018 23:46:41 GMT
>     > WARNING:   Connection: close
>     > WARNING:   Content-Length: 423
>     > WARNING:
>     > WARNING:   <?xml
>     >
>     version="1.0"?><interface-response><Command>SETDNSHOST</Command><Language>eng</Language><ErrCount>1</ErrCount><errors><Err1>Domain
>     > name not
>     >
>     found</Err1></errors><ResponseCount>1</ResponseCount><responses><response><ResponseNumber>316153</ResponseNumber><ResponseString>Validation
>     > error; not found; domain
>     >
>     name(s)</ResponseString></response></responses><Done>true</Done><debug><![CDATA[]]></debug></interface-response>
>     >
>     > FAILED:   updating \updated: Invalid reply.
>     >
>     >
>     > My ddclient config looks like this:
>     >
>     >
>     > ## NameCheap (namecheap.com <http://namecheap.com>)
>     > ##
>     > use=web, web=dynamicdns.park-your-domain.com/getip
>     <http://dynamicdns.park-your-domain.com/getip> \
>     > protocol=namecheap                              \
>     > server=dynamicdns.park-your-domain.com
>     <http://dynamicdns.park-your-domain.com>  \
>     > login=adams-lan.org <http://adams-lan.org>                     \
>     > password=xxxxxxxxxxxxxxxxxxxxxxxxxx               \updated to
>     below key
>     > on 9/16/18
>     >
>     >
>     > That's they way the individual I chatted with at namecheap had me
>     > configure it. I noticed that information at ddclient's wiki was
>     slightly
>     > different:
>     >
>     >
>     > protocol=namecheap
>     > server=dynamicdns.park-your-domain.com
>     <http://dynamicdns.park-your-domain.com>         \defaults to
>     > dynamicdns.park-your-domain.com
>     <http://dynamicdns.park-your-domain.com>
>     > login=adams-lan.org <http://adams-lan.org>    \login name and
>     password registered with the service
>     > password=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>     > adams-lan.org <http://adams-lan.org>  \the host registered with
>     the service.
>     >
>     >
>     > Unfortunately, that didn't work either.
>     >
>     > Can anybody shed some light on this for me?
>     >
>     > I would appreciate it.
>     >
>     > Thanks.
>     >
>     >
>     > Mark
>     >
>     >
> 
>     The backslash isn't a place where you put comment, it should be before
>     the end of the line, indicating a continous line.  That's why you get
>     "host=\updated" in the URL sent the server.  It uses the part after the
>     password as hostname.  That's also why you get a "Domain not found" in
>     the response.
> 
>     Kind regards,
> 
>     Wim.
> 
> 
>     _______________________________________________
>     Ddclient-support mailing list
>     Ddc...@li...
>     <mailto:Ddc...@li...>
>     https://lists.sourceforge.net/lists/listinfo/ddclient-support
> 
> 
> 
> -- 
> Mark Adams
> 
> READ CAREFULLY. By reading this email, you agree, on behalf of your
> employer, to release me from all obligations and waivers arising from
> any and all NON-NEGOTIATED agreements, licenses, terms-of-service,
> shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure,
> non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have
> entered into with your employer, its partners, licensors, agents and
> assigns, in perpetuity, without prejudice to my ongoing rights and
> privileges. You further represent that you have the authority to release
> me from any BOGUS AGREEMENTS on behalf of your employer.

Re: [Ddclient-support] ddclient updates not working -- invalid logins

[wimpunk <wi...@us...>]

On 10/5/18 1:57 AM, Mark Adams wrote:
> Greetings!
> 
> Around the end of July my automatic ddns updates stopped working. My
> domain is registered at namecheap.com and I was on chat with them for a
> couple of hours before they finally told me that they can't help me and
> provided a link to information about manually updating my ddns. I find
> that a bit unsatisfying and am considering moving my registrar but I
> wanted to see if I could get this sorted out first.
> 
> The trouble is in here somewhere. This is the output from "ddclient
> --force" on my server:
> 
> # ddclient -force
> WARNING:  skipping host: @: 'login=' is an invalid login.
> WARNING:  skipping host: @: 'login=' is an invalid login.
> WARNING:  SENT:
> http://dynamicdns.park-your-domain.com/update?host=\updated&domain=to&password=below&ip=64.130.86.93
> 
> WARNING:  REPLIED: HTTP/1.1 200 OK
> WARNING:   Cache-Control: private
> WARNING:   Content-Type: text/html
> WARNING:   Set-Cookie: ASPSESSIONIDSQTCDSAT=KEDDLBADPKAMKAMMIDKCCODF;
> path=/
> WARNING:   Date: Thu, 04 Oct 2018 23:46:41 GMT
> WARNING:   Connection: close
> WARNING:   Content-Length: 423
> WARNING:
> WARNING:   <?xml
> version="1.0"?><interface-response><Command>SETDNSHOST</Command><Language>eng</Language><ErrCount>1</ErrCount><errors><Err1>Domain
> name not
> found</Err1></errors><ResponseCount>1</ResponseCount><responses><response><ResponseNumber>316153</ResponseNumber><ResponseString>Validation
> error; not found; domain
> name(s)</ResponseString></response></responses><Done>true</Done><debug><![CDATA[]]></debug></interface-response>
> 
> FAILED:   updating \updated: Invalid reply.
> 
> 
> My ddclient config looks like this:
> 
> 
> ## NameCheap (namecheap.com)
> ##
> use=web, web=dynamicdns.park-your-domain.com/getip \
> protocol=namecheap                              \
> server=dynamicdns.park-your-domain.com  \
> login=adams-lan.org                     \
> password=xxxxxxxxxxxxxxxxxxxxxxxxxx               \updated to below key
> on 9/16/18
> 
> 
> That's they way the individual I chatted with at namecheap had me
> configure it. I noticed that information at ddclient's wiki was slightly
> different:
> 
> 
> protocol=namecheap
> server=dynamicdns.park-your-domain.com         \defaults to
> dynamicdns.park-your-domain.com
> login=adams-lan.org    \login name and password registered with the service
> password=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> adams-lan.org  \the host registered with the service.
> 
> 
> Unfortunately, that didn't work either.
> 
> Can anybody shed some light on this for me?
> 
> I would appreciate it.
> 
> Thanks.
> 
> 
> Mark
> 
> 

The backslash isn't a place where you put comment, it should be before
the end of the line, indicating a continous line.  That's why you get
"host=\updated" in the URL sent the server.  It uses the part after the
password as hostname.  That's also why you get a "Domain not found" in
the response.

Kind regards,

Wim.

[Ddclient-support] ddclient updates not working -- invalid logins

[Mark A. <ma...@gm...>]

Greetings!

Around the end of July my automatic ddns updates stopped working. My 
domain is registered at namecheap.com and I was on chat with them for a 
couple of hours before they finally told me that they can't help me and 
provided a link to information about manually updating my ddns. I find 
that a bit unsatisfying and am considering moving my registrar but I 
wanted to see if I could get this sorted out first.

The trouble is in here somewhere. This is the output from "ddclient 
--force" on my server:

# ddclient -force
WARNING:  skipping host: @: 'login=' is an invalid login.
WARNING:  skipping host: @: 'login=' is an invalid login.
WARNING:  SENT: 
http://dynamicdns.park-your-domain.com/update?host=\updated&domain=to&password=below&ip=64.130.86.93
WARNING:  REPLIED: HTTP/1.1 200 OK
WARNING:   Cache-Control: private
WARNING:   Content-Type: text/html
WARNING:   Set-Cookie: ASPSESSIONIDSQTCDSAT=KEDDLBADPKAMKAMMIDKCCODF; path=/
WARNING:   Date: Thu, 04 Oct 2018 23:46:41 GMT
WARNING:   Connection: close
WARNING:   Content-Length: 423
WARNING:
WARNING:   <?xml 
version="1.0"?><interface-response><Command>SETDNSHOST</Command><Language>eng</Language><ErrCount>1</ErrCount><errors><Err1>Domain 
name not 
found</Err1></errors><ResponseCount>1</ResponseCount><responses><response><ResponseNumber>316153</ResponseNumber><ResponseString>Validation 
error; not found; domain 
name(s)</ResponseString></response></responses><Done>true</Done><debug><![CDATA[]]></debug></interface-response>
FAILED:   updating \updated: Invalid reply.


My ddclient config looks like this:


## NameCheap (namecheap.com)
##
use=web, web=dynamicdns.park-your-domain.com/getip \
protocol=namecheap                              \
server=dynamicdns.park-your-domain.com  \
login=adams-lan.org                     \
password=xxxxxxxxxxxxxxxxxxxxxxxxxx               \updated to below key 
on 9/16/18


That's they way the individual I chatted with at namecheap had me 
configure it. I noticed that information at ddclient's wiki was slightly 
different:


protocol=namecheap
server=dynamicdns.park-your-domain.com         \defaults to 
dynamicdns.park-your-domain.com
login=adams-lan.org    \login name and password registered with the service
password=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
adams-lan.org  \the host registered with the service.


Unfortunately, that didn't work either.

Can anybody shed some light on this for me?

I would appreciate it.

Thanks.


Mark

[Ddclient-support] Can not pass IPv6 IP via -ip option

[Andrey V. <an...@va...>]

Hello *,

 

I'd like to use static ipv6 to update DDNS. I run ddclient using command
line argument "-ip", for example:

 

ddclient -daemon=0 -use=ip -ip=2001:16b8:22e1:1c00:aaaa:aaaa:aaaa:aaaa -ipv6
-verbose -debug -host=myhost.domain

 

ddclient logs following:

-------------

WARNING:  found neither ipv4 nor ipv6 address

DEBUG:    get_ip: using ip, ip reports <undefined>

WARNING:  unable to determine IP address

------------

 

So far I understand it's a bug that can be fixed with following patch:

 

------------

--- orig/ddclient       2018-08-29 20:51:54.000000000 +0200

+++ ddclient    2018-09-16 17:53:24.553246958 +0200

@@ -2162,7 +2162,7 @@

     if ($use eq 'ip') {

        $ip  = opt('ip', $h);

        $arg = 'ip';

-

+       $reply=$ip;

     } elsif ($use eq 'if') {

        $skip  = opt('if-skip', $h)  || '';

        $reply = `ifconfig $arg 2> /dev/null`;

------------

 

Best regards

--

Andrey Vakhitov

 

E-Mail:   <mailto:an...@va...> an...@va...
Stuttgart, Germany

 

[Ddclient-support] ddclient stopped working for cloudflare

[Ellie R. <ell...@gm...>]

Hi,
subject line pretty much says it all. Whenever I try to update my domain 
on cloudflare with ddclient I now get this: WARNING:  file 
/data/ddclient/ddclient.cache, line 4: Invalid Value for keyword 'ip' = ''.

There were no upgrade of ddclient or perl between the moment where it 
worked and when it stopped working, which makes me think it could be an 
api change. I also deleted the cache file several times to let ddclient 
recreate it, and this is still happening.
If anyone can provide any insight into this I would be grateful.
Thanks !

Sorry for the noise, I realized I had misconfigured my smtp server, it 
is fixed now.

[Ddclient-support] Please help with ddclient config for subdomain resolution through DDNS on Google Domains

[Joshua P. <fs...@ho...>]

Can I get assistance. I'm installing on a home system and don't have a static IP address. To work around that, on my CentOS system I've installed ddclient with the hopes of utilizing DDNS from my Google Domains account.


In my Google Domains, I've created two records. They are as follows:


1. A synthetic Dynamic DNS record with an '@' (without the single quotes) in the data field.

2. A custom resource CNAME record, with '*' (without the single quotes) for the name and the domain name in the data field so this is supposed to be acting as a wildcard record.


The synthetic record receives the IP address updates from the ddclient service that's running on my codius server. Ideally I'll be able to resolve my domain, ex. xrp.haus, as well as codius.xrp.haus, or contract.codius.xrp.com<http://contract.codius.xrp.com>. Unfortunately, my configuration doesn't seem to resolve. I can resolve the domain, xrp.haus, but not any subdomains that are prefixed onto that.


Below is my ddclient config. Any help would be appreciated. Thanks in advance!


#########################################

daemon=600

syslog=yes

mail-failure=root

pid=/var/run/ddclient/ddclient.pid

ssl=yes


use=web, web=checkip.dyndns.org/<http://checkip.dyndns.org/>, web-skip='IP Address'


#Google Domains Configuration Below

protocol=dyndns2

use=web

server=domains.google.com<http://domains.google.com>

ssl=yes

wildcard=yes

login=IJ3xxxxxxxxxxrIs

password='ycbxxxxxxxxxxakg'

xrp.haus

[Ddclient-support] [ddclient/ddclient]

[GitHub <no...@gi...>]

  Branch: refs/tags/v3.9.0
  Home:   https://github.com/ddclient/ddclient

      **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.

[Ddclient-support] [ddclient/ddclient] 02c983: Preparing the release of v3.9.0

[GitHub <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/ddclient/ddclient
  Commit: 02c983a991531f5bb1637701b9d0c399094bba29
      https://github.com/ddclient/ddclient/commit/02c983a991531f5bb1637701b9d0c399094bba29
  Author: wimpunk <wi...@us...>
  Date:   2018-08-09 (Thu, 09 Aug 2018)

  Changed paths:
    M ChangeLog
    M README.md
    M RELEASENOTE
    M ddclient

  Log Message:
  -----------
  Preparing the release of v3.9.0



      **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.

[Ddclient-support] [ddclient/ddclient] 118cad: Specify port number properly to 'nsupdate' (#58)

[GitHub <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/ddclient/ddclient
  Commit: 118cad0f1173ff3c4fcfe463b23feb35a2b06191
      https://github.com/ddclient/ddclient/commit/118cad0f1173ff3c4fcfe463b23feb35a2b06191
  Author: Kevin P. Fleming <kpf...@us...>
  Date:   2018-07-25 (Wed, 25 Jul 2018)

  Changed paths:
    M ddclient

  Log Message:
  -----------
  Specify port number properly to 'nsupdate' (#58)

If a port number is included in the 'server' configuration item,
ddclient allows a port number to be specified by appending a colon
and the port number to the server's name or IPv4 address. However,
nsupdate does not support this syntax, it requires the port number
to be separated from the server name/address by whitespace.

Signed-off-by: Kevin P. Fleming <ke...@km...>



      **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.

[Ddclient-support] [ddclient/ddclient] ab706c: Fix sample Cloudflare config (#57)

[GitHub <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/ddclient/ddclient
  Commit: ab706ccae039cc5144c6ef77700285f5c1c4645e
      https://github.com/ddclient/ddclient/commit/ab706ccae039cc5144c6ef77700285f5c1c4645e
  Author: Denton Liu <liu...@gm...>
  Date:   2018-06-25 (Mon, 25 Jun 2018)

  Changed paths:
    M sample-etc_ddclient.conf

  Log Message:
  -----------
  Fix sample Cloudflare config (#57)

The extra comma bleeds into the API request sent to Cloudflare and, as a
result, causes it to fail. Reordering the options and removing the comma
at the password fliield, fixes this problem.



      **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.

[Ddclient-support] [ddclient/ddclient] 7e850b: Support IPv6 for CloudFlare

[GitHub <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/ddclient/ddclient
  Commit: 7e850b7560f7e6929aa30345c9e13f10bc25640b
      https://github.com/ddclient/ddclient/commit/7e850b7560f7e6929aa30345c9e13f10bc25640b
  Author: David Ryskalczyk <dav...@gm...>
  Date:   2018-05-20 (Sun, 20 May 2018)

  Changed paths:
    M ddclient

  Log Message:
  -----------
  Support IPv6 for CloudFlare


  Commit: ec2acfb1f3a8043ac993765a1709e5798ff7d267
      https://github.com/ddclient/ddclient/commit/ec2acfb1f3a8043ac993765a1709e5798ff7d267
  Author: wimpunk <wi...@us...>
  Date:   2018-05-23 (Wed, 23 May 2018)

  Changed paths:
    M ddclient

  Log Message:
  -----------
  Support IPv6 for CloudFlare

This makes the Cloudflare support IPv6-aware.

Ideally, A and AAAA records would be updated in one shot, as CloudFlare has a 5 minute throttling limit for API calls that change records.

Merge pull request #56 from d235j/cloudflare-ipv6


Compare: https://github.com/ddclient/ddclient/compare/c176457e1286...ec2acfb1f3a8
      **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.

[Ddclient-support] [ddclient/ddclient] 1da21d: name cheap support https now

[GitHub <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/ddclient/ddclient
  Commit: 1da21d82e130a16f7e6fe7a334adbaa923beb4ce
      https://github.com/ddclient/ddclient/commit/1da21d82e130a16f7e6fe7a334adbaa923beb4ce
  Author: Wujun Zhou <wzh...@gm...>
  Date:   2018-05-17 (Thu, 17 May 2018)

  Changed paths:
    M ddclient

  Log Message:
  -----------
  name cheap support https now

>From name cheap it seems http is supported now.
https://www.namecheap.com/support/knowledgebase/article.aspx/29/11/how-to-use-the-browser-to-dynamically-update-hosts-ip

Since the password was send on plaintext, https should be used


  Commit: c176457e128629d0f6e58c25ba429db784c61ca7
      https://github.com/ddclient/ddclient/commit/c176457e128629d0f6e58c25ba429db784c61ca7
  Author: wimpunk <wi...@us...>
  Date:   2018-05-23 (Wed, 23 May 2018)

  Changed paths:
    M ddclient

  Log Message:
  -----------
  name cheap support https now

Merge pull request #55 from wjzhou/wzhou/namecheap-https


Compare: https://github.com/ddclient/ddclient/compare/3dd20541247f...c176457e1286
      **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.