Comments on: Tomato firmware: Dynamic DNS with dynDNS.org

By: Hari

Hari — Mon, 03 May 2010 03:18:22 +0000

Does this method work if tomato router is setup in client mode behind the main router? I guess this depends on whether tomato takes the help of external services to figure out what the public IP is (like the services running on windows do).

I currently have tomato router with the public ip and ddns works fine without a schedule. But I do get the reminders from dyndns.com to click on a link to avoid expiration. Does a schedule to do a force update of ddns avoid this (in a sense, auto extend the expiration)?

By: Eric

Eric — Thu, 05 Mar 2009 00:15:12 +0000

I have mine set to every 12 hours. It updates both my DynDNS hosts. I have been running it like that for the last 6 months and I have not yet been banned. My IP rarely ever changes (Once a month) but if it changes, my downtime is minimal.

By: Jeff

Jeff — Sat, 14 Feb 2009 09:36:33 +0000

Eric’s tip is exactly what I was looking for. I have a problem where my no-ip domain expires because my IP address changes so infrequently. Using this method, I can ensure that the domain stays active even when my IP address is nearly static.

Maybe I’m missing it, but where is a good reference for these kinds of commands in Tomato?

By: Pascal

Pascal — Sun, 08 Feb 2009 02:07:51 +0000

In what situation do you need to schedule this? I never had to force an update because as soon as the router get a connection, it updates dyndns.org automatically… I guess you have an ISP that changes your IP address frequently?

Pascal.

By: Eric

Eric — Sun, 08 Feb 2009 00:54:37 +0000

A handy tip that I found

Go to scheduler -> Custom 1

ddns-update 0 force
ddns-update 1 force

It will automatically update your DDNS automatically and you can change the frequency.