Joshua Penix wrote:
On Jan 9, 2008, at 1:22 PM, [EMAIL PROTECTED] wrote:
I installed ddclient and it appears to be doing it the "wrong" way.
You configured ddclient the wrong way.
Assuming dyndns.org, they provide a URL that prints out your current
external IP:
http://checkip.dyndns.org
There's a 'use' line in the default ddclient.conf config file made
specifically to take advantage of this:
use=web, web=checkip.dyndns.org/, web-skip='IP Address' # found after IP
Address
With that configured, ddclient will check that webpage hourly and
compare the result with the last known IP address. If it changes, it
updates dyndns.org.
Read through that config file and you'll get the idea. It works quite
well from behind NAT.
That said, if you have a router with a dynamic DNS client built in, why
not use that?
--Joshua Penix http://www.binarytribe.com
I ran into such a problem the other day.
The modems supplied by AT&T (at least for their low-end DSL service
users - i.e. $10/mo.) do not expose the actual WAN address to the
router. The router only sees the LAN address (in this case 192.168.1.64)
assigned it by the DSL modem, which cannot be modified at the DSL modem.
When the router (Netgear FVS318v1) sends it's "WAN" address to
dnydns.org, the service sets the new IP address to the non-routeable
address.
However, as far as I can tell, at least in WinXP, using the DNS updater
client passes the correct IP address to the service. I assume that if
Windows can do it, then so can a Linux client-side program.
--
Best Regards,
~DJA.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
