ddclient-support — Support for ddclient

[Ddclient-support] OVH stop working

[Josu L. <jos...@gm...>]

Hello, I have been using ddclient with OVH dyndns service:
http://guide.ovh.com/DynDns

But since some days ago it does not work, this is the log output:

# tail /var/log/daemon.log
Jul 20 16:33:07 htpc3 ddclient[2234]: WARNING:  file
/tmp/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''
Jul 20 16:33:08 htpc3 ddclient[2234]: WARNING:  skipping update of
sub.domain.com from <nothing> to xxx.xxx.229.126.
Jul 20 16:33:08 htpc3 ddclient[2234]: WARNING:   last updated <never>
but last attempt on Fri Jul 20 16:28:07 2012 failed.
Jul 20 16:33:08 htpc3 ddclient[2234]: WARNING:   Wait at least 5
minutes between update attempts.
Jul 20 16:38:08 htpc3 ddclient[2234]: WARNING:  cannot send to
www.ovh.com:443 (Bad file descriptor).
Jul 20 16:38:08 htpc3 ddclient[2234]: FAILED:   updating
sub.domain.com: Could not connect to www.ovh.com.
Jul 20 16:43:08 htpc3 ddclient[2234]: WARNING:  file
/tmp/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''
Jul 20 16:43:08 htpc3 ddclient[2234]: WARNING:  skipping update of
sub.domain.com from <nothing> to xxx.xxx.229.126.
Jul 20 16:43:08 htpc3 ddclient[2234]: WARNING:   last updated <never>
but last attempt on Fri Jul 20 16:38:08 2012 failed.
Jul 20 16:43:08 htpc3 ddclient[2234]: WARNING:   Wait at least 5
minutes between update attempts.

This is my configuration file:

# cat /etc/ddclient.conf

protocol=dyndns2
pid=/var/run/ddclient.pid
cache=/tmp/ddclient.cache
use=web, web=checkip.dyndns.org/, web-skip='Current IP Address:'
server=www.ovh.com
ssl=yes
login=domain.com-domain
password='mypassword'
sub.domain.com

Anyone using OVH with ddclient?

Thanks and best regards.

-- 
Josu Lazkano

[Ddclient-support] ddclient continuously updating ip address

[<co...@cc...>]

Hi.  I have been using ddclient-3.6.3 for a long time, but starting
yesterday, it was updating my ip address every minute or so -- it would
update in a cycle to the last ip used and the previous one.  I don't
think the actual ip changed, at least the provider didn't think so, so
can you tell me what it checks when it wakes up and any hints as to why
its doing this?

Thanks in advance for your help.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         co...@cc...

[Ddclient-support] Duplicate tries to update

[Koenraad L. <ddc...@de...>]

Hi,

Since a while ddclient tries more than one time to update my domains. 
Since I'm having stability problems with my dsl-line I risk being locked 
out of zoneedit.com.

This is what I get at the second try :

WARNING:  file /var/cache/ddclient/ddclient.cache, line 4: Invalid Value 
for keyword 'ip' = '77.109.102.164/'
SUCCESS:  updating xxx.de-brouwerij.be: IP address set to 77.109.102.164 
(201: No records need updating.)

regards,
    ddclient@neptunus (version 3.8.0)

I do have two domains I update with ddclient, with different dns-services.

Is this a bug ?

Thanks,

Koenraad Lelong

[Ddclient-support] Support for IPv6 (patch)

[Felix L. <fel...@gm...>]

For some reason I cannot read all messages in this thread, but I would like
to second Eduardo's request for the new ipv6 feature.

>From the abundance of ipv6 addresses it may seem that 'ddclient' has no use
in the future, but that is not true.  Several ipv6 transition scenarios,
including Teredo, involve dynamic addresses (although no NAT).

One could, and perhaps should, use 'ddclient' for relaying corresponding
updates to dynamic DNS.

Eduardo's solution to separate ipv4 and ipv6 makes great sense, because one
can serve both protocols both from different equipment.  Many free hosting
plans provide only ipv4.  Serving ipv6, on the other hand, is uncomplicated
even when behind NAT and requires no port forwarding.

Hurricane Electric (he.net) offers dynamic DNS for A and AAAA records.  I
would like to use 'ddclient' for that purpose.

Sincerely,
Felix

Re: [Ddclient-support] Support for IPv6 (patch)

[Eduardo T. <etr...@gm...>]

>> No, it doesn't, you're right.  It's simply that Debian doesn't have
>> /sbin int its path for non root users.  You have to add it or call
>> /sbin/ifconfig directly but you do not need root privileges.
> 
> That seems broken.  The directory /sbin typically contains various
> utilities that normal users can legitimately execute to gather
> information, like dmesg, mount, ping, route, sysctl...
> In /usr/sbin, there is more useful stuff like apm, arp, chgrp,
> dig, fs, groupinfo, host, iostat, etc. etc.
> So deleting *sbin from the PATH looks rather stupid.

If your interested in understanding the reasoning please check this old
discussion[1], with the relevant information from the FHS.  It's by no
means stupid.  Arguable maybe, not stupid.

> Hell, deleting *sbin from the PATH breaks sudo(8) on top of that.
> Users can't even do things like "sudo halt" any longer if
> they dont have *sbin in their PATH.

sudo lives in /usr/bin!!  So this has nothing to do with it.  Please
check your assertions.

> So no, a PATH not containing /sbin is never sane, and i don't think
> we need to care about it (it is well known that a default Debian
> system usually requires some manual reconfiguration before it
> becomes usable).  Maybe the documentation should mention
> that running ddclient(8) requires a sane PATH giving access to
> common utilities (including ifconfig(8)).

I think I'd rather go back to ddclient, your knowledge or assumptions on
Debian and sane defaults and usability seem to be a little ... either
biased or outdated, just like the previous IPv6 ones.  I just said a
normal user in Debian does not have /sbin by default in the path.
Ddclient *runs as root*.  So that's not a problem!

> A usev6 option might indeed make sense, allowing different strategies
> for v4 and v6 to be used concurrently.  However, in that case, this
> chunk looks suspicious:
> 
> +			my $use = '';
> +		        $ipv6 = 1 if (defined $config{$h}{'usev6'});
> +			if ($ipv6) {
> +			    $use = $config{$h}{'usev6'} || opt('usev6');
> +			}
> +			else {
> +			    $use = $config{$h}{'use'} || opt('use');
> +			}
> 
> This will only allow to set either v4 or v6, right?

For each entry, yes, that is the whole idea.  To treat ipv6 hosts as
another host.  For me it's hard to pretend it's like an MX or something
like that and add a parameter.  It's hard because there is all the
strategy stuff.

> Maybe it's possible to support both in parallel?

Yes, by adding two configuration entries.

> It may require slightly more changes.
> If not, then it might be better to support just "use = ipv6',
> "use = ifv6", "use = webv6".

I started out the way you are suggesting.  But I really didn't like the
idea of namespace pollution, if you see what I mean.  "ifv6", "ipv6",
"webv6".  And they would do basically the same thing as their non-6
counterparts.  I'd call it configuration noise.  Say you want to have
both ipv4 and ipv6:

You can have two lines like this:

protocol=dyndns2
usev6=if, if=teredo
server=members.dyndns.org
login=user
password='my$password'
myteredohost.dyndns.tv

protocol=dyndns2
use=if, if=ppp0
server=members.dyndns.org
login=user
password='my$password'
myteredohost.dyndns.tv

Then you would have, at the same time, updates for ipv4 and ipv6.  Even
better, you *could* set different parameters to each one, whatever they
might be.

*BUT* the program hashes the definitions based on
'myteredohost.dyndns.tv' (as far as I can see, I've already stated I'm
not that fluent in perl).  In my original message I mentioned that
problem and  explicitily said I didn't know how to work around it.

I believe that it's better to have two definitions, one for ipv4 and one
ipv6 (as in the example above) and just a new keyword.  I looks cleaner.

> If ddclient(8) is to support ipv6 at all, them allowing to set both

It already does :).  For dyndns at least in four or five Debian/Ubuntu
computers.  Please keep in mind that not necessarily everybody will take
the same path as afraid.org / dyndns, that is parsing the address and
deciding which record to update (A or AAAAA).  Some of them may decide
to have a completely different update url, for example.

> families in parallel seems more attractive than being forced to
> choose either, so i'd prefer the use/usev6 direction.

Lets say that to achieve the same result it looks nicer and it's easier
both on humans and on the parsing code:

use=if, if=ppp0
usev6=if, if=teredo
use=ip, ip=204.23.12.99

[use, usev6, if, ip]

than:

use=if, if=ppp0
use=ifv6, ifv6=teredo
use=ipv6, ipv6=2001:0::2

[use, usev6, if, ifv6, ip, ipv6]

>> It's your call to ignore the patch, rewrite it or do as you wish,
> 
> Sorry, i don't have time for detailed testing and polishing
> this afternoon, but perhaps later, or perhaps others have...

It's ok, no hurry.  It works for me and has already paid off.  Just
wante to share the results back.  The tone of my sentence was because I
was in part reacting on the perceived uselessness of the patch.  That's
settled.

Eduardo.

[1] http://lists.debian.org/debian-devel/1999/12/msg00946.html

Re: [Ddclient-support] Support for IPv6 (patch)

[Eduardo T. <etr...@gm...>]

>> I wrote a little patch for 3.8.1 to support IPv6 on the two services
>> I know that can handle it.
> 
> I'm not sure i understand.
> 
> DynDNS for IPv6 sounds like a terrible misconcept, a contradiction
> all in itself.

I'm using a teredo client (transition technology) so I get an dynamic
IPv6 over an IPv4 tunnel, I'd like to be able to access it.  I need a
name for that because doing:

ssh user@[2001:0000:4136:e378:8000:63bf:3fff:fdd2]

is not practical or, at least not so simple as:

ssh us...@te...

when you take into account that the host is miles aways from me, behind
a NAT router that changes its IPv4 address periodically.  I'm actually
(and happily) using a name for dynamic IPv6 right now.  So much for the
misconcept or contradiction.  IPv4 just would not work, or I would have
to setup a VPN for incoming connections ( and believe me it's a lot
easier to do apt-get install miredo, and that's it).

> I thought the whole point of IPv6 is to have enough addresses
> such that everybody can have their own, proper addresses?

We found the misconcept and inner contradiction.  There it is.  Routing
and latency should ring an alarm with that idea of yours, not to mention
routing size tables.  If you fly from the US to France, even if possible
(as with IPv4) I doubt you would want to keep "your own" IPv6 address
from the other side of the ocean for your mobile or your notebook.  And
no, nobody would care to change transatlantic routes just for a user.
You would most likely want to pick up the hotel room or the university
IPv6 address, or the airport wireless one and then, you host will be
more easily found by using a name (dyndns to the rescue!). Of course
there are extensions for handling mobile, multihoming and staff like
that in IPv6 (also for IPv4) for example [1][2] but they are overkill
for most individuals.

Everybody is going to be addressable in IPv6, but nobody garantees you
will always have the same address wherever you go!!  That's at least
naïve if you consider the impact that would have for moving users on the
size of the backbone routing tables.

So, may I suggest that the misconception lies on your side?  If we had
enough IPv4 you would consider dynamic DNS "a terribly misconcept"?  The
key concept here is not *address* but *dynamic*.

>> "ip -6 addr list" instead of "ifconfig" because I find it easier
>> to parse and it doesn't need root privileges (Debian box).
> 
> Don't do that.  The /sbin/ip command is utterly non-portable
> and purely Linux-only, so it should not be used for anything
> outside purely Linux-only contexts.

Ok, if you think this can make it into mainline I can change that.

> Besides, using ifconfig(8) to query an IP address does not
> require root privileges.

No, it doesn't, you're right.  It's simply that Debian doesn't have
/sbin int its path for non root users.  You have to add it or call
/sbin/ifconfig directly but you do not need root privileges.

> Even if the basic concept would make any sense, i don't see
> any patch anywhere.

The list didn't just let it through, please care to read the next
message on the same subject to find the link to the actual patch.  I
copy it here[3] just in case.

About the basic concept, you might want to reconsider it.  I'm not
proposing it, I'm using it already from dyndns.com and I've used it from
afraid.org.  There will be dynamic IPv6, and not only during transition
(which will last long enough).  Happily somebody is already letting us
avoid things like 2001:0000:4136:e378:8000:63bf:3fff:fdd2 and using
names instead.  Teredo and 6to4 (on dynamic IPv4) are not rare, I just
tried to add support to ddclient because that's the client I use and
love, I tried to take the least invasive route (just a keyword).

It's your call to ignore the patch, rewrite it or do as you wish,
dynamic dns for IPv6 is out there, it's used and eventually, if it
proves useful it will be soported, if not by upstream as a patch in
Debian, with ifconfig not iproute2, I get it.  In any case, I suggest
you revisit the whole IPv6 concept.

Friendly, Eduardo.

[1] Mobility Support in IPv6 http://tools.ietf.org/html/rfc6275
[2] Provider-independent address space
https://www.ripe.net/ripe/docs/ripe-510#2e
[3]
https://sourceforge.net/tracker/?func=detail&aid=3407066&group_id=116817&atid=676131

[Ddclient-support] Support for IPv6 (patch)

[Eduardo T. <etr...@gm...>]

Hi,

I wrote a little patch for 3.8.1 to support IPv6 on the two services I 
know that can handle it.  Both dyndns and freedns automatically 
recognize the type of address being passed to them and use it to update 
the A or the AAAA record.

I added the "usev6" variable, that works exactly as the "use" one.  So, 
if you are using dynds and change use/usev6 on your existing definition 
*and* you have a global IPv6 address you're all set.

For "usev6" only the "ip" and "if" strategies are implemented and the 
"if" one uses "ip -6 addr list" instead of "ifconfig" because I find it 
easier to parse and it doesn't need root privileges (Debian box).

So far the patch works for dyndns without problems, for an IPv6-only 
host (well, it does have IPv4 but its a private address, the IPv6 
address is public and comes from miredo/teredo).

Since the program hashes the hosts on the dynamic domain, it is not 
possible to update IPv4 and IPv6 on the same service with the same 
configuration file.  I'm not that fluent in perl so I guess it's better 
for the actual programmers to sort that one out.

Freedns forces you to have an IPv4 record that is used to build the 
update url.  The IPv6 update on that url works but the DNS servers can 
take a long time to notice it.  It's tricky.

I hope it helps somebody, it took me a while to figure it out.

Eduardo.

Re: [Ddclient-support] Is there a way to have ddclient force an update once a day?

[Wim V. <wi...@gm...>]

On Tue, Sep 6, 2011 at 8:00 PM, Cary Lewis <car...@gm...> wrote:
> Dyndns doesn't like spurious updates (indication of abuse of free
> accounts), but if you don't update at least once a month, your account
> gets suspended.
>
> So I was wondering if there was a way to configure ddclient to do this.
>

There is the max-interval for that.  By default ddclient updates
dyndns every max-interval time which defaults to 25 days.

> I suppose I could set up a cron job that would stop the daemon once a
> day, do a -force update, and then restart the daemon, but I was hoping
> there was a way to do all of this with ddclient running as daemon.
>
> Any thoughts?

Yep, I think the last one is a very bad idea. :-)

[Ddclient-support] Is there a way to have ddclient force an update once a day?

[Cary L. <car...@gm...>]

Dyndns doesn't like spurious updates (indication of abuse of free
accounts), but if you don't update at least once a month, your account
gets suspended.

So I was wondering if there was a way to configure ddclient to do this.

I suppose I could set up a cron job that would stop the daemon once a
day, do a -force update, and then restart the daemon, but I was hoping
there was a way to do all of this with ddclient running as daemon.

Any thoughts?

Re: [Ddclient-support] Log file

[Ingo S. <isc...@as...>]

Hi Josu,

Josu Lazkano schrieb am Fri, May 20, 2011 at 09:10:36PM +0200:

> May 19 20:10:27 htpc ddclient[1726]: WARNING:  cannot connect to
> checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
> 'checkip.dyndns.org'

The IO::Socket::INET library tries to resolve the host
name 'checkip.dyndns.org' into an IP address and that fails.
Probably, you are starting ddclient early in the boot process
before you have name resolution up and running.

Make sure that while booting, you start the various services
in a good order, and don't start anything before the required
prerequisites are working.  In particular, first start up your
interfaces - dial-in, probably? - then start up the DNS resolver
(which may be automatic, some PPP and some DHCP client programs
automatically create the file /etc/resolv.conf when receiving the
necessary information from the peer) and only start ddclient when
you are sure that DNS resolution is working properly, in particular
that /etc/resolv.conf is in place and contains working name
server adresses of your Internet service provider.

How to achieve that in detail is outside the scope of this list,
ask the supplier of your PPP, DHCP or booting system - whatever
you happen to be using - for support if you fail to fix that yourself.

Yours,
  Ingo

-- 
Ingo Schwarze <isc...@as...> | Software Engineer
Astaro GmbH & Co. KG | www.astaro.com | 76227 Karlsruhe | Germany

Re: [Ddclient-support] Log file

[Wim V. <wi...@gm...>]

On Fri, May 20, 2011 at 9:10 PM, Josu Lazkano <jos...@gm...> wrote:
> 2011/5/20 Torsten Landschoff <t.l...@gm...>:
>> On Fri, 2011-05-20 at 10:21 +0200, Josu Lazkano wrote:
>>> Hello. I just installed ddclient on a Debian server and I want to know
>>> if there a option to have a log file to check the daemon.
>>
>> There is the -syslog option (enabled by default on Debian) which uses
>> the system log daemon to log information. The result is usually found
>> in /var/log/daemon.log:
>>
>> root@pluto:/home/torsten# grep ddclient /var/log/daemon.log
>> May 17 04:18:53 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.28.190.18
>> May 18 04:07:55 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.18.50.23
>> May 19 04:09:11 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.18.80.46
>>
>> Good luck!
>>
>> Torsten
>>
>>
>>
>
> Thanks again, I check the /car/log/daemon.log and it is there!!!
>
> May 19 20:10:27 htpc ddclient[1726]: WARNING:  cannot connect to
> checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
> 'checkip.dyndns.org'
> May 19 20:16:07 htpc ddclient[1726]: WARNING:  cannot connect to
> checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
> 'checkip.dyndns.org'
> May 19 20:21:10 htpc ddclient[1726]: SUCCESS:  updating

I've tried some others but most have give errors to.  Btw, how fast do
you run ddclient?  There is a rate limit for the service so there is a
possibility you get blocked by there service.
In my experience the best thing you can do is getting your IP from your router.

Regards,

wim.

Re: [Ddclient-support] Log file

[Josu L. <jos...@gm...>]

2011/5/20 Torsten Landschoff <t.l...@gm...>:
> On Fri, 2011-05-20 at 10:21 +0200, Josu Lazkano wrote:
>> Hello. I just installed ddclient on a Debian server and I want to know
>> if there a option to have a log file to check the daemon.
>
> There is the -syslog option (enabled by default on Debian) which uses
> the system log daemon to log information. The result is usually found
> in /var/log/daemon.log:
>
> root@pluto:/home/torsten# grep ddclient /var/log/daemon.log
> May 17 04:18:53 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.28.190.18
> May 18 04:07:55 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.18.50.23
> May 19 04:09:11 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.18.80.46
>
> Good luck!
>
> Torsten
>
>
>

Thanks again, I check the /car/log/daemon.log and it is there!!!

May 19 20:10:27 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 19 20:16:07 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 19 20:21:10 htpc ddclient[1726]: SUCCESS:  updating
subdomain.domain.com: good: IP address set to 188.77.225.4
May 20 01:57:08 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 02:02:48 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 02:08:28 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 02:14:08 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 02:19:48 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 02:24:50 htpc ddclient[1726]: SUCCESS:  updating
subdomain.domain.com: good: IP address set to 188.77.252.109
May 20 03:10:32 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 03:15:33 htpc ddclient[1726]: SUCCESS:  updating
subdomain.domain.com: good: IP address set to 188.77.237.45

I am getting some warnings, I will change the ipcheck page, any alternative?

Is possible to add a log file on the config to output all data to and
specific file?

Thanks for your help.

Kind regards.


-- 
Josu Lazkano

Re: [Ddclient-support] Unsubscribe

[wim v. <wi...@ti...>]

On Fri, May 20, 2011 at 5:15 PM, Steve Knapp <sp...@wi...> wrote:
> Unsubscribe
>
>
>
> T.H. Huxley: "Try to learn something about everything and everything about
> something."
>
>
>
> Oscar Levant: "I envy people who drink. At least they have something to
> blame everything on."
>
>

See https://lists.sourceforge.net/lists/listinfo/ddclient-support on
how to unsubscribe the list.

wimpunk.

Re: [Ddclient-support] Log file

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

By default ddclient can log to syslog.  You can add a filter to syslog
to log to your preferred named.  Check your syslog documentation.

wimpunk.

On Fri, May 20, 2011 at 7:56 PM, Josu Lazkano <jos...@gm...> wrote:
> Thanks for the reply, I want to check if the service is log in well on
> the dyndns server.
>
> Something on /var/log/ddclient.log
>
> Best regards.
>
> 2011/5/20 wimpunk <wi...@us...>:
>> On Fri, 2011-05-20 at 10:21 +0200, Josu Lazkano wrote:
>>> Hello. I just installed ddclient on a Debian server and I want to know
>>> if there a option to have a log file to check the daemon.
>>>
>>> Thank and best regards.
>>>
>>
>> What do you mean with a log file to check the daemon?  What part do you
>> want to check?
>>
>> regards,
>>
>> wimpunk.
>>
>>
>>
>
>
>
> --
> Josu Lazkano
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Ddclient-support mailing list
> Ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddclient-support
>

Re: [Ddclient-support] Log file

[Josu L. <jos...@gm...>]

Thanks for the reply, I want to check if the service is log in well on
the dyndns server.

Something on /var/log/ddclient.log

Best regards.

2011/5/20 wimpunk <wi...@us...>:
> On Fri, 2011-05-20 at 10:21 +0200, Josu Lazkano wrote:
>> Hello. I just installed ddclient on a Debian server and I want to know
>> if there a option to have a log file to check the daemon.
>>
>> Thank and best regards.
>>
>
> What do you mean with a log file to check the daemon?  What part do you
> want to check?
>
> regards,
>
> wimpunk.
>
>
>



-- 
Josu Lazkano

[Ddclient-support] Unsubscribe

[Steve K. <sp...@wi...>]

Unsubscribe

 

T.H. Huxley: "Try to learn something about everything and everything about
something." 



Oscar Levant: "I envy people who drink. At least they have something to
blame everything on." 

[Ddclient-support] Log file

[Josu L. <jos...@gm...>]

Hello. I just installed ddclient on a Debian server and I want to know
if there a option to have a log file to check the daemon.

Thank and best regards.

-- 
Josu Lazkano

[Ddclient-support] Log file

[Josu L. <jos...@gm...>]

Hello. I just installed ddclient on a Debian server and I want to know
if there a option to have a log file to check the daemon.

Thank and best regards.

-- 
Josu Lazkano

Re: [Ddclient-support] ddclient debug advice

[Wim V. <wi...@gm...>]

It is all in the README file, see the TROUBLESHOOTING section.  Run
ddclient -daemon=0 -debug -verbose -noquiet and see what is happening.

Regards,

wimpunk.


On Mon, Mar 21, 2011 at 11:20 PM, Dennis Putnam <da...@be...> wrote:
> I have a 'ddclient' that only updates 'dnydns.com' when I enter
> 'ddclient stop' and 'ddclient start'. I get nothing in my syslog at all
> (good or bad) and I don't know how to go about debugging this. For
> reference here is my redacted 'ddclient.conf' which was generated by the
> dyndns.com web site.
>
> ## ddclient configuration file
> daemon=300
> # check every 300 seconds
> syslog=yes
> # log update msgs to syslog
> mail-failure=my...@my... # Mail failed updates to user
> pid=/var/run/ddclient.pid
> # record PID in file.
> ## Detect IP with our CheckIP server
> use=web, web=checkip.dyndns.com/, web-skip='IP Address'
> ## DynDNS username and password here
> login=uuuuuuuuuu
> password=ppppppppp
> ## Default options
> protocol=dyndns2
> server=members.dyndns.org
> ## Dynamic DNS hosts
> myhost1.dyndns-ip.com,myhost2.dyndns-ip.com
>
> Any advice as to how to debug this would be appreciated.
>
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Ddclient-support mailing list
> Ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddclient-support
>

[Ddclient-support] ddclient debug advice

[Dennis P. <da...@be...>]

I have a 'ddclient' that only updates 'dnydns.com' when I enter
'ddclient stop' and 'ddclient start'. I get nothing in my syslog at all
(good or bad) and I don't know how to go about debugging this. For
reference here is my redacted 'ddclient.conf' which was generated by the
dyndns.com web site.

## ddclient configuration file
daemon=300
# check every 300 seconds
syslog=yes
# log update msgs to syslog
mail-failure=my...@my... # Mail failed updates to user
pid=/var/run/ddclient.pid
# record PID in file.
## Detect IP with our CheckIP server
use=web, web=checkip.dyndns.com/, web-skip='IP Address'
## DynDNS username and password here
login=uuuuuuuuuu
password=ppppppppp
## Default options
protocol=dyndns2
server=members.dyndns.org
## Dynamic DNS hosts
myhost1.dyndns-ip.com,myhost2.dyndns-ip.com

Any advice as to how to debug this would be appreciated.

[Ddclient-support] William Oquendo invited you to Dropbox

[Dropbox <no-...@dr...>]

William Oquendo wants you to use Dropbox to sync and share files online and across computers.

Get started here: http://www.dropbox.com/link/20.SyHMS3mE1x/NjYyMzU5OTUxNw?src=referrals_ab_bulk7

- The Dropbox Team

____________________________________________________ 
To stop receiving invites from Dropbox, please go to http://www.dropbox.com/bl/f7d9c494dd6c/ddclient-support%40lists.sourceforge.net

Re: [Ddclient-support] Proxy credentials

[William O. <woq...@gm...>]

Dear Ingo,

Thank you very much for giving me this full detailed answer, even knowing
you are busy =) Unfortunately I am no a perl programmer. I will be looking
forward for this feature.

Best regards / Cordialmente,

--
William Oquendo
Phd Candidate
Simulation Of Physical Systems Group
National University of Colombia
Linux User # 321481
*********************
Este correo puede carecer de tildes o eñes ya que el teclado no contiene
estos caracteres. Presento excusas por eso.

*********************



On Mon, Jun 14, 2010 at 3:22 PM, Ingo Schwarze <isc...@as...> wrote:

> Hi William,
>
> William Oquendo schrieb am Thu, Jun 10, 2010 at 06:52:27PM -0500:
>
> > Dear all, I have been searching in google and in the forums with no
> > success about the following:
>
> Yes, ddclient is not famous for its documentation.
> As a general rule, your best bet for understanding what the
> program does is reading the source code, even though that's
> rather entangled and not easy to understand due to all those
> global variables.
>
> > I have a computer behind a University proxy, and I need to know the
> > internal ip all the time.  I need to specify the CREDENTIALS for
> > a proxy in ddclient, since I always get error 407 proxy authentication
> > error.
>
> Judging from the function geturl(), my impression is that ddclient
> plainly doesn't support proxies that require authentication.
> In the function geturl(), i see the DynDNS credentials being passed
> on to the DynDNS server, but i don't see any variables that could
> hold proxy credentials.
>
> > I have already configured the proxy in both the command line and
> > the ddclient.conf file, but I always got the error 407, proxy
> > authentication required.  In a desperate try, I wrote the full
> > line for the proxy:
> > userproxy:pas...@pr...:8080
>
> Oh, you mean into the "proxy" configuration variable?
> I don't think that will work, here is the parser for that
> variable, you find it in geturl():
>
>    $proxy  =~ s%^https?://%%i;
>    $peer   = $proxy || $server;
>    $peer   =~ s%/.*%%;
>    $port   = $peer;
>    $port   =~ s%^.*:%%;
>    $port   = $default_port unless $port =~ /^\d+$/;
>    $peer   =~ s%:.*$%%;
>
> So, in a nutshell, everything behind the last colon is taken
> as the port, everything before the first colon as the proxy host,
> and everything in between is discarded.
> Thus, ...
>
> > and ddclient quits an  error message related to "Error connecting
> > to proxy userproxy:8080" !!
>
>  ... small wonder, from the point of view of ddclient,
>
>  proxy = userproxy:pas...@pr...:8080
>
> is just the same as
>
>  proxy = userproxy:8080
>
> > Even the http_proxy var is present.
>
>   $ grep -i http_proxy ddclient
>  $
>
> That won't work, the ddclient program ignores that environment
> variable.
>
> > I really appreciate your help. I just simply want to know how to
> > configure the proxy credentials in ddclient.
>
> You are out of luck, ddclient doesn't seem to have that feature,
> and i don't feel like coding it right now, i'm too busy elsewhere.
> But i would estimate that an experienced Perl programmer might
> add the feature in about one day of work, perhaps even quicker
> if s/he is familiar with the ddclient code.
>
> Sorry that i can't really help you,
>  Ingo
>
> --
> Ingo Schwarze <isc...@as...> | Software Engineer
> Astaro GmbH & Co. KG | www.astaro.com | 76227 Karlsruhe | Germany
>

Re: [Ddclient-support] Proxy credentials

[Ingo S. <isc...@as...>]

Hi William,

William Oquendo schrieb am Thu, Jun 10, 2010 at 06:52:27PM -0500:

> Dear all, I have been searching in google and in the forums with no
> success about the following:

Yes, ddclient is not famous for its documentation.
As a general rule, your best bet for understanding what the
program does is reading the source code, even though that's
rather entangled and not easy to understand due to all those
global variables.

> I have a computer behind a University proxy, and I need to know the
> internal ip all the time.  I need to specify the CREDENTIALS for
> a proxy in ddclient, since I always get error 407 proxy authentication
> error.

Judging from the function geturl(), my impression is that ddclient
plainly doesn't support proxies that require authentication.
In the function geturl(), i see the DynDNS credentials being passed
on to the DynDNS server, but i don't see any variables that could
hold proxy credentials.

> I have already configured the proxy in both the command line and
> the ddclient.conf file, but I always got the error 407, proxy
> authentication required.  In a desperate try, I wrote the full
> line for the proxy:
> userproxy:pas...@pr...:8080

Oh, you mean into the "proxy" configuration variable?
I don't think that will work, here is the parser for that
variable, you find it in geturl():

    $proxy  =~ s%^https?://%%i;
    $peer   = $proxy || $server;
    $peer   =~ s%/.*%%;
    $port   = $peer;
    $port   =~ s%^.*:%%;
    $port   = $default_port unless $port =~ /^\d+$/;
    $peer   =~ s%:.*$%%;

So, in a nutshell, everything behind the last colon is taken
as the port, everything before the first colon as the proxy host,
and everything in between is discarded.
Thus, ...

> and ddclient quits an  error message related to "Error connecting
> to proxy userproxy:8080" !!

 ... small wonder, from the point of view of ddclient,

  proxy = userproxy:pas...@pr...:8080

is just the same as

  proxy = userproxy:8080

> Even the http_proxy var is present.

  $ grep -i http_proxy ddclient 
  $

That won't work, the ddclient program ignores that environment
variable.

> I really appreciate your help. I just simply want to know how to
> configure the proxy credentials in ddclient.

You are out of luck, ddclient doesn't seem to have that feature,
and i don't feel like coding it right now, i'm too busy elsewhere.
But i would estimate that an experienced Perl programmer might
add the feature in about one day of work, perhaps even quicker
if s/he is familiar with the ddclient code.

Sorry that i can't really help you,
  Ingo

-- 
Ingo Schwarze <isc...@as...> | Software Engineer
Astaro GmbH & Co. KG | www.astaro.com | 76227 Karlsruhe | Germany

[Ddclient-support] Proxy credentials

[William O. <woq...@gm...>]

Dear all, I have been searching in google and in the forums with no success
about the following: I have a computer behind a University proxy, and I need
to know the internal ip all the time. I need to specify the CREDENTIALS for
a proxy in ddclient, since I always get error 407 proxy authentication
error.
I have already configured the proxy in both the command line and the
ddclient.conf file, but I always got the error 407, proxy authentication
required. In a desperate try, I wrote the full line for the proxy:
userproxy:pas...@pr...:8080
and ddclient quits an  error message related to "Error connecting to proxy
userproxy:8080" !!
Even the http_proxy var is present.

I really appreciate your help. I just simply want to know how to configure
the proxy credentials in ddclient.

Thanks in advance.

Best regards / Cordialmente,

--
William Oquendo
Phd Candidate
Simulation Of Physical Systems Group
National University of Colombia
Linux User # 321481
*********************
Este correo puede carecer de tildes o eñes ya que el teclado no contiene
estos caracteres. Presento excusas por eso.

*********************

Re: [Ddclient-support] DDClient Detecting a Second Gateway (Provider)???

[Ingo S. <isc...@as...>]

Hi Larry,

i admit i didn't look at the captured packets,
but the following explanation looks plausible in general:

Larry Houston wrote on Wed, Feb 03, 2010 at 03:55:41PM -0500:

> possible explanations as to why this Asymmetric Routing has occurred?

Usually, DNS changes do not take effect immediately.
It is very common to employ caching on DNS servers.
Sometimes, it takes up to a full day until some caches expire.

Thus, if you change DNS information on the DynDNS server,
some servers may pick it up fairly quickly, but some others
may take more time.  In your case, even very small delays can
make a difference.

In general, the routing of a response IP packet does not depend
on the routing of the packet it responds to.
Thus, if you send a packet via the new route to a host using a caching
DNS server still having your old IP address in its cache, the response
packets will arrive via the old route, possibly triggering another switch
of the address you have registered with DynDNS.

Again, this is just one relatively simple, plausible explanation.
The real effects may be more involved; both DNS and routing can be
quite tricky.

In any case, i think combining "use=web" in your ddclient configuration
with multiple Internet uplinks is asking for trouble - in fact, just
the trouble you are experiencing, unstable DNS and routing.
The "use=web" method may be sufficient for trivial setups,
but it's not that useful once things get more complicated.
You might wish to look at other configuration methods;
as i said, there are plenty.

So far, i see no indication that you suffer from a bug in ddclient.

Yours,
  Ingo

--
Ingo Schwarze <isc...@as...> | Software Engineer | Framework Team
Astaro AG | www.astaro.com | 76227 Karlsruhe | Germany