EasyDNS doesn't update until I click edit and save.



  • Every once in a while my easyDNS account in pfSense shows an outdated cached IP address in red while my DynDNS account shows my current IP address in green. These are both on the same pfSense box for the same WAN interface so I don't understand why one service updates in time and the other doesn't. I need to edit and save my pfSense account in order to force it to update the IP address.



  • While I understand easyDNS is supposed to be easy, you would be better off using Bind9 if you can.



  • Can you post log snips for both a failed update cycle and one that works?



  • I'm unable to find Dynamic DNS logs.



  • @KurianOfBorg:

    I'm unable to find Dynamic DNS logs.

    OK, post the output from pfSense shell command```
    clog /var/log/system.log | grep -i dns

    
    Here is an extract from my system (IP address obfuscated)  May  6 01:01:01 pfsense php: : DynDns: updatedns() starting
    May  6 01:01:01 pfsense php: : DynDns debug information: xxx.29.zzz.164 extracted from local system.
    May  6 01:01:01 pfsense php: : DynDns: Current WAN IP: xxx.29.zzz.164 Cached IP: xxx.29.zzz.164
    May  6 01:01:01 pfsense php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.


  • I found that the error occurs when easyDNS refuses an update with TOO SOON. pfSense never attempts to update the IP address again until the next change and easyDNS's address is outdated.



  • Is this going to be fixed? Do I file a bug report for this?



  • pfSense should update addresses every 25 days or on a change.

    How soon is "TOO SOON" and how long is "TOO LONG"?



  • @wallabybob:

    pfSense should update addresses every 25 days or on a change.

    How soon is "TOO SOON" and how long is "TOO LONG"?

    Updating more than once within 600 seconds results in a TOO SOON error. The problem is it never attempts to wait and update the address again when receiving this error. So unless the address changes yet again after 600 seconds, it will never be updated.

    Basically it doesn't retry after a delay when receiving a TOO SOON error.