dnsomatic: dnsexit error
I have 4 services set up in dnsomatic. Only one of the 4 is not working, dnsexit. I am 100% sure it is configured correctly in dnsomatic. I can go directly to the dnsexit web site and successfully manually update.
One thing I notice - when I first login at dnsexit, it always says ...
Your session has expired
click here to the login screen
so effectively I have to login twice. Is that why dnsomatic is failing? How to fix?
dnsomatic.jpg
-
Attached the history log for dnsexit. Seems like is has worked in the past, stopped working recently. That may coincide with my having to login twice when accessing dnsexit account by browser.
I already had email sending enabled "on errors only", but never received any emails (I also checked my spam folder - nothing). Changed that now to "Always".
dnsomatic_01.jpg
dnsomatic_02.jpg -
I see now. The error is "4=IP not changed". It seems you attempted to update your dnsexit hostname, although the IP address has not changed. Most DDNS services don't like such behaviour. If your IP address indeed didn't change, you don't need to worry about this. If your IP address changed, then you should raise a support ticket with OpenDNS. They may need to modify the dnsexit interface at DNS-O-Matic.
The problem is merely with the notification e-mails. I also don't get them recently anymore. This seems to be a glitch, and one of us may open a support ticket with OpenDNS because of this.
-
It's updated by inadyn startup script in the dd-wrt router, currently configured with a forced update of 10 days.
inadyn --username XXXX --password XXXX --alias all.dnsomatic.com --dyndns_server_name updates.dnsomatic.com --dyndns_server_url /nic/update? --update_period_sec 60 --forced_update_period 864000 --wildcard --background
-
Hmm, but in your DNS-O-Matic log it indicates that there are more updates than just every 10 days. You may refer to an inadyn forum to see why this is, i.e. if it is a bug and what can be done to get it right. For example, you may have to make use of the inadyn config file instead of the parameters in the command line.
-
I was trying to give the short version of events :)
dd-wrt has a built in DDNS configuration. It seemed to not be working, so I updated dd-wrt to newest version and tried it again with different configurations, couldn't get it to work. So then added inadyn scripting and had to tweak that to get that to work. In among all that were plenty of router reboots and script changes, so, dnsomatic updates (when they were working) happened more frequently than every 10 days. I have more or less finished all the router updating now, so don't expect another forced update for 8 days.
-
All looks good now, the inadyn script is working, dnsomatic updated all services including dnsexit. Thanks.
dnsomatic_03.jpg
Please sign in to leave a comment.
Comments
11 comments