[SOLVED]Issue with DNS-O-Matic Updates



  • I'm unable to force a DNS-O-Matic update.  I have verified that my username/password is correct.  This is the log:

    
    Mar 10 18:39:05 pfsense check_reload_status: syncing firewall
    Mar 10 18:39:09 pfsense check_reload_status: syncing firewall
    Mar 10 18:39:50 pfsense check_reload_status: syncing firewall
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DynDns: Running updatedns()
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DynDns: updatedns() starting
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DynDns: _detectChange() starting.
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DynDns: _checkIP() starting.
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DynDns debug information: xxx.xxx.xxx.xxx extracted from local system.
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DynDns: Current WAN IP: xxx.xxx.xxx.xxx
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DynDns: Cached IP: 0.0.0.0
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DynDns debug information: DynDns: cacheIP != wan_ip.  Updating. Cached IP: 0.0.0.0 WAN IP: xxx.xxx.xxx.xxx 
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DynDns: DynDns _update() starting.
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DNS-O-Matic: DNS update() starting.
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DynDns: DynDns _checkStatus() starting.
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DynDns: Current Service: dnsomatic
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DNS-O-Matic: PAYLOAD:  <title>301 Moved</title> 
    
    # 301 Moved
    
     The document has moved [here](https://mail.google.com/mail/).^M ^M
    Mar 10 18:39:50 pfsense php: /services_dyndns_edit.php: DNS-O-Matic: (Unknown Response)
    
    

    My DynDNS updates just fine.  Any help would be appreciated.  Thanks!

    EDIT:  Removed my IP address.

    EDIT 2:  Additionally, I first had the DynDNS entry in place and that worked fine.  I then added the DNS-O-Matic entry and it has always displayed (in all red) 0.0.0.0



  • What URL are you using for the DNS-O-Matic updates?

    Does your DNS-O-Matic password include any characters with special meaning in URLs (e.g. ":", "/", "?" etc)?

    Your log suggests there might be a problem with the URL:

    DNS-O-Matic: PAYLOAD: <title>301 Moved</title>

    301 Moved

    The document has moved



  • @wallabybob:

    What URL are you using for the DNS-O-Matic updates?

    Does your DNS-O-Matic password include any characters with special meaning in URLs (e.g. ":", "/", "?" etc)?

    There is an @ symbol in my password for DNS-O-Matic

    @wallabybob:

    Your log suggests there might be a problem with the URL:

    DNS-O-Matic: PAYLOAD: <title>301 Moved</title>

    301 Moved

    The document has moved

    When I'm in the Dynamic DNS page on my pfSense box, I simply choose DNS-O-Matic.  I don't choose a different host name?  On the USERNAME field, I am putting username@gmail.com (as that's how I have to log in to DNS-O-MATIC).  Thanks for your help!  I'll try changing my password on DNS-O-Matic…however, it wasn't working before I changed the password to include the '@'.



  • @CNLiberal:

    however, it wasn't working before I changed the password to include the '@'.

    It wouldn't necessarily be failing then for the same reason as it is failing now.

    The DNS-O-matic documentation for updates by URL says the URL should be of the form (see http://www.dnsomatic.com/wiki/api) https://username:password@updates.dnsomatic.com/nic/update?hostname=yourhostname&myip=ipaddress&wildcard=NOCHG&mx=NOCHG&backmx=NOCHG

    It looks to me that if the username includes a ":" or the password includes an "@" it could confuse the URL parser.

    What hostname did you specify in pfSense? (I use all.dnsomatic.com) to get all my registrations with DNS-O-matic updated.)

    I suggest you give yourself a new DNS-O-matic password of only letters and digits and try again. If you still get an error then best provide the error report.

    It might also be worth reading the referenced API document and having a try to update it manually through a browser access so you get the hang of what should go in the different fields in the pfSense form.



  • It appears to be an issue with having a username with an '@' in it.  Once I removed that, everything started to work.  Thanks for your assistance and patience!

    Jim


Log in to reply