On Mon, 2006-07-31 at 21:59 -0400, George Stoianov wrote:
On 7/31/06, Ken Schneider <suse-list2@bout-tyme.net> wrote:
On Sun, 2006-07-30 at 19:28 -0800, John Andersen wrote:
On Sunday 30 July 2006 14:54, George Stoianov wrote:
I have solved my problem as my router is now doing the work of updating with the dyndns sever, but if you can provide advise on what might be wrong, maybe a dependent package, I will be very thankful.
If your router sits upstream of your linux box then that is the proper place to do it. Why complicate your machine with another daemon?
What does "man ddclient" say?
I use ddclient for two domains and it works flawlessly. Actually ddclient is a perl script that needs to be edited (well documented) and adjusted for your setup and then just run it, it sleeps for the time period you set as well so it doesn't upset the folks at dyndns.org.
Really I thought it worked out of the box according to this http://www.novell.com/coolsolutions/feature/15845.html
george
Well... out of the box it knows nothing about your domain or your login credentials at dyndns.org so it does need to be configured. As I recall the perl script didn't properly support the WRT54G router and I needed to fine tune it as the script insisted on wanting to supply a username which the router does -not- use. Edit the /etc/ddclient.conf file to suit your needs. I also use ddclient because I manage two domains. If I only had one to manage I would use the support built into the router. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998