SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Sat, 5 Nov 2005 02:23:34 PST8
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: DynDNS setup (was: please test my ftp server - MarkO)

Content Type: text/plain

Steven Levine wrote:
>
> Peter Skye said:
> >Does anyone know of a dyndns.org update client
> >which lets you put the IP on the command line?
>
> Why would you want to do this?

So I can call the update client with the ISP's current DHCP IP for my
DSL line.

> What make you think that your setup is in any way special?

I didn't think it was special. Did I say "special" somewhere?

> There are any number of clients which check the
> well-known URLs that will return your WAN IP.

I don't need a URL. All I have to do is ask the SMC Barricade. I've
had a log running on it since 2004-Mar-31 -- want some of my old IP
addresses?

Getting my IP isn't a problem. I'm just looking for an easy way to post
it to my DNS provider.

> Inadyn will probably be the easiest
> for you to find since it is on Hobbes.

I looked at inadyn before I asked my question. The readme.html file
indicated that it watches the machine on which inadyn is running but not
an external firewall. From the first paragraph of the inadyn
readme.html file:

"... periodically checks whether the IP address stored by the DNS
server
is the real current address of the machine that is running INADYN."

If the docs say "the real current address of the machine that is running
INADYN" then it seems unlikely that it also checks somewhere else (such
as an external firewall).

The readme does say farther down that inadyn

- updates the correct IP address even behind a NAT router
- supports access via http proxy

but according to the docs up to that point these have to be running on
the same machine as inadyn.

But I appreciate you suggesting that I take another look at inadyn. If
a potential user keeps reading, in the parameters section it shows

'--ip_server_name[:port] url': The client IP is detected by calling
'url' from this 'ip_server_name:port'. Defaults to checkip.dyndns.org:80
/.

and a quick test of http://checkip.dyndns.org:80/ does return my current
ISP DHCP IP.

Obviously, then, the inadyn doc needs a fixup ('cause it's wrong!) and
the "--ip_server_name" parameter *does* allow me to effectively put the
current IP address on the command line. Exactly what I was looking for.

And inadyn works with ZoneEdit as well as DynDNS, which is good because
I just moved my DNS services from GoDaddy to ZoneEdit.

Thanks much, when I get back from San Diego I'll give inadyn a try.
It's going to take a little experimenting since the docs don't give any
example of how to use the "--ip_server_name" parameter *and* there
apparently isn't any keyword to identify it -- I guess if inadyn can't
figure out what a parameter is then it assumes it is an IP server.
Mighty abnormal way of having someone specify a parameter.

I do see that the inadyn logging does not work on OS/2. It says so in
the docs (see the --syslog parameter).

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================

Return to [ 05 | November | 2005 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.