I am currently using dyndns.org, but I am not choosing it during the
configuration but using an hourly cron job instead, and the client util
(ipcheck.py) from their site. My /etc/cron.hourly/ipcheck looks like:
#run the first line on a new install, from /root and swap the line remarks
for normal
Don't know if this is relavent, but I noticed a typo in the refresh-ddns cron.weekly
job:
After the my upgrade the cron job wanted to execute
/sbin/e-smith/events/actions/update-dns
which didn't exist on my system, instead I changed it to
/etc/e-smith/events/actions/update-dns
and
On Mon, Nov 26, 2001 at 08:02:44PM +, Martin Warnes wrote:
Don't know if this is relavent, but I noticed a typo in the refresh-ddns cron.weekly
job:
After the my upgrade the cron job wanted to execute
/sbin/e-smith/events/actions/update-dns
which didn't exist on my system, instead I
I'm using the dyndns freebee service but I suspect my address changes
infrequently though I had suspicions of a problem as I'm having to do a
manual update about once a month. I'm using SME 5 and I've just edited my
file as you suggest so I'll post again if I get any problems etc.
:¬} Nigel
Strangely I had been using it up until a few months ago (same
dyndns.org) for my home e-smith box and it worked fine. I was on 4.1
though, perhaps it had broken after that.
JP
- Original Message -
From: Lionel [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, November 25, 2001 7:14
On Mon, Nov 26, 2001 at 12:14:23AM +1100, Lionel [EMAIL PROTECTED] wrote:
[...]
Which is functionally the same, but without the 'system=dyndns' field
that was screwing up the updates.
Could you provide details of exactly what is failing (logs, etc.) to
[EMAIL PROTECTED] ?
I don't know if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
From: Gordon Rowell [mailto:[EMAIL PROTECTED]]
I think you'll find others are as well, Dan Brown provided the
script,
Been a while since I did anything with it, though. The problem is
that dyndns.org has three services: dynamic DNS
On Mon, 26 Nov 2001 00:14, Lionel wrote:
Just letting you know that I've finally gotten around to investigating
the problem with this feature that I discovered some months ago:
[...]
Which is functionally the same, but without the 'system=dyndns' field
that was screwing up the updates.
I
I have v5 running with the free dyndns custom dns working from the e-smith
for my primary domain. It was functional before I upgraded but after the
upgrade to v 5 I had to put a third party client in to do the updates, I
thought that it was because I was using 2 domains on the same box, however
On Mon, Nov 26, 2001 at 03:11:43PM +1100, Rob Hillis [EMAIL PROTECTED] wrote:
[...]
I noticed the same when I upgraded to SMEv5, although since I need to ensure
that my backup MX record is also recorded, I've been using one of their own
update clients for almost all the time since I
On Mon, 26 Nov 2001 17:16, Gordon Rowell wrote:
I noticed the same when I upgraded to SMEv5, although since I need to
ensure that my backup MX record is also recorded, I've been using one of
their own update clients for almost all the time since I upgraded...
Please help us by reporting
On Mon, Nov 26, 2001 at 06:13:35PM +1100, Rob Hillis [EMAIL PROTECTED] wrote:
[...]
As someone who's best described as relatively new to Linux (i.e. if I haven't
seen the problem before and learnt how to fix it, I'm stuffed) I had no idea
what was causing the problem. I don't remember
12 matches
Mail list logo
