DDNS Problem
- This topic has 9 replies, 2 voices, and was last updated 6 years, 12 months ago by
Jeff Hatch.
-
AuthorPosts
-
April 10, 2018 at 4:54 am #23057
Asier Gomez
ParticipantI have a conduit multitech with Firmware 1.4.3.
I am trying to configure DDNS but after configuring all parameters, and forcing updating, DDNS is disabled appears, any idea?April 10, 2018 at 7:44 am #23063Jeff Hatch
KeymasterAsier,
Let’s start with the simple stuff:
Assuming you enabled through the Web UI, did you hit the Submit button, and do a Save and Restart?
Jeff
April 10, 2018 at 7:54 am #23064Asier Gomez
ParticipantYes,
I hit Submit, Save and Restart.
And nothing, when i hit Force Update:
– Update Started
– DDNS disabledBR
April 10, 2018 at 8:16 am #23065Jeff Hatch
KeymasterWhich ddns service are you using? On the DDNS page in the Configuration section, after you save and restart is the Enabled check-box still checked? Does the Conduit have Internet access?
I do not currently have a valid ddns account so when I run inadyn at the command line I get:
admin@mtcdt:/var/run# inadyn -V –config /var/run/inadyn.conf
Tue Apr 10 13:07:48 2018: Error parsing option -V
admin@mtcdt:/var/run# inadyn –config /var/run/inadyn.conf
Tue Apr 10 13:07:57 2018: Missing username in account 1
Tue Apr 10 13:07:57 2018: Missing password in account 1
Tue Apr 10 13:07:57 2018: No valid DDNS setup exists.The inadyn process does not seem to be logging any of these messages, so you will not get any feedback without running it by hand. Here is my inadyn.conf after configuring:
admin@mtcdt:/var/run# cat inadyn.conf
background
verbose 1
startup-delay 0
logfile /var/log/ddns.log
pidfile /var/run/ddns.pid
forced-update 2419200
system default@dyndns.org
alias multitech.com
ip_server_name checkip.dyndns.org:80 /The inadyn process appears to be reaching out to dyndns, but since I don’t have anything set up I am getting the “No valid DDNS setup exists.”
Jeff
April 10, 2018 at 9:11 am #23066Asier Gomez
ParticipantI have executed the same commands, with several providers. The result is teh same. For example… for duckdns.org ….
LOG FILE
Tue Apr 10 16:05:06 2018: FORCED_UPDATE command received, updating now.
Tue Apr 10 16:05:06 2018: Checking for IP# change, connecting to cpherreramancha.duckdns.org(81.45.34.209:80)
Tue Apr 10 16:05:07 2018: Checked my IP, return code: 42
Tue Apr 10 16:05:07 2018: Will retry again in 600 sec…
~
INADYN.CONFbackground
verbose 1
startup-delay 0
logfile /var/log/ddns.log
pidfile /var/run/ddns.pid
forced-update 2419200
system default@duckdns.org
username cp.herrera.mancha@gmail.com
password ————————————-
alias cpherreramancha.duckdns.org
ip_server_name cpherreramancha.duckdns.org:80 /But it is the same with no-ip and others.
🙁
April 10, 2018 at 9:39 am #23067Jeff Hatch
KeymasterCould you perform an “inadyn –version” to verify which version of inadyn is on AEP 1.4.3 (I don’t have a unit running that version at the moment). The error code #42 corresponds to the following error in inadyn for version 1.99.3:
RC_DYNDNS_INVALID_RSP_FROM_IP_SERVER
From what I can tell, this means inadyn doesn’t like the server’s response.
Jeff
April 10, 2018 at 9:52 am #23068Asier Gomez
ParticipantInadyn version 1.99.13 — Dynamic DNS update client.
By the way, I have public IP
April 10, 2018 at 2:36 pm #23069Jeff Hatch
KeymasterI took a couple minutes and looked up RC_DYNDNS_INVALID_RSP_FROM_IP_SERVER with Google. A large number of people that have run into this issue seem to have had connectivity issues to the DDNS server. Have you tried connecting with a browser to see if you get any kind of response?
Jeff
April 11, 2018 at 3:16 am #23071Asier Gomez
ParticipantI have updated to 1.4.16 version with same result.
Is it possible updating Inadyn ? how?April 11, 2018 at 8:07 am #23074Jeff Hatch
KeymasterPlease file a Multitech Support Portal case at https://support.multitech.com. They will be able to help you at a more in-depth level. Have you tried using wireshark or tcpdump to verify that connectivity with duckdns is working?
Jeff
-
AuthorPosts
- You must be logged in to reply to this topic.