1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

What is the expected behavior of the Tomato DynDNS client?

Discussion in 'Tomato Firmware' started by bripab007, Dec 4, 2008.

  1. bripab007

    bripab007 Network Guru Member

    I'm using DynDNS client in Tomato to maintain my external dynamic DNS name, and I'm wondering what the Tomato behavior is for this client.

    For the drop-down at the top of the page, I'm using the default "Use WAN IP Address (recommended)."

    I'm assuming this means that, if Tomato detects a WAN IP change, then it'll try to update that change with DynDNS' records, otherwise, it'll do an update to their records once every 28 days, regardless of IP change.

    Is that correct?

    Has anyone ever noticed the Tomato client not updating automatically every 28 days?
     
  2. Victek

    Victek Network Guru Member

    I got a renewal and new advice "successful" every time that my public IP changes, it works in real time. Unfortunately I'm updating firmwares every few days, so, no experience on due date.

    One example:

    Last IP Address Mon 01 Dec 2008 10:19:25 PM CET:
    87.221.xx.xxx
    Last Result Mon 01 Dec 2008 10:19:25 PM CET:
    Update successful
     
  3. jhwker

    jhwker Addicted to LI Member

    It has always sent a renew before 30 days went by even if the IP remained constant. I use it and have never had any problem.
     
  4. bripab007

    bripab007 Network Guru Member

    Okay, yes, I assumed that was its expected behavior, however, a friend of mine running Tomato (1.19 or 1.20, can't recall) had his DynDNS client not update after a WAN IP change recently.

    I had him do the force update option in Tomato web gui, it updated, and asked him to let me know what happens with it in 30 days, so we'll see.
     
  5. ndoggac

    ndoggac Network Guru Member

    i looked at the cron in V1.22 and it had a forced dynDNS update scheduled for I believe only once a year (might have been 6 months?) if the WAN IP address doesn't change. I put in an init script to also add a cron job to force an update every 2 weeks whether the WAN was upated or not. Here is the command...I got this from another thread here on linksysinfo.

    cru a ddnsupd "0 2 * * 0 ddns-update 0 force"

    I looked this up as a result of getting the warning email from dynDNS for inactivity, notifying me that they would eliminate my account if I didn't log in.
     
  6. jhwker

    jhwker Addicted to LI Member

    The last time my Dynamic DNS updated was 11/29 at 16:14. Looking at my cron it is currently set to do a update at 16:14 on 12/27 Twenty eight days after the last update which is what it is supposed to do, does not look broke to me...
    14 16 27 12 * ddns-update 0 force #ddnsf0#
    min hour day month week
     
  7. Kiwi8

    Kiwi8 LI Guru Member

    U can try registering your DNS operators with DNS-O-Matic. They seem to refresh the various DNS operators often enough that I do not get prompts from them anymore.
     
  8. jyavenard

    jyavenard Network Guru Member

    Interesting, I received the same email this morning..
    Weird that we would both receive at the same time.. too much of a coincidence ...
     
  9. jersully

    jersully LI Guru Member

    The same has happened to me once. It appears to have just been a fluke. It's worked every since.
     
  10. bripab007

    bripab007 Network Guru Member

    So, we've got some people saying they've found the code within Tomato that forces the update every 28 days, regardless of whether or not the IP's changed, and we've got other people saying the code says 6-12months?

    Where is the truth? :-D

    EDIT: So, I just checked my cron jobs, and, yes, mine's set to update on the 12/22/2008, which is 28 days after my last DynDNS update. I believe it's working as intended.
     

Share This Page