I know this is resurrecting a really old topic, but I have finally obtained some rather useful information in regards to DNS-O-MATIC. This was discussed elsewhere in the Marvell forum. If you are having problems with dnsomatic you can also try http but specify port 443. Posted: Sat 19:42 Post subject: Re: Problem solved!Ĭonfirmed working for me as well! THANK YOU! Posted: Sat 11:18 Post subject: Re: Problem solved!Īny idea why this issue has started occurring in the first place? Pogo - A minimal level of ability is expected and needed.Īt some point, people just get plain tired of this place.īecause they are tired of bottom-feeders and the same old hat. "Life is but a fleeting moment, a vapor that vanishes quickly All is vanity" Wiki should be updated, unless someone mucks with my edit. Great news that the old 1.96 GUI does work with https. I've attached a screen shot for posterity. () No more need for cron or startup scripts. Leaving everything else as-is, adding port 443 in the URL works like a champ. They said this:Ĭan you try updating your router/application to send updates to using port 443 ()? We no longer allow updates to this service using port 80. Posted: Mon 22:39 Post subject: Problem solved! R7000 - Gateway & WiFi - DDWRT r51140 StdĮ2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531 R7000 - Gateway & WiFi & WireGuard - DDWRT r51887 StdĮ3000 - Station Bridge - DDWRT r49626 Mega K4.4 R7000 - Wired ISP 4K IPTV Gateway - DDWRT r51887 Std Home Network on Telus 1Gb PureFibre - 10GbE Copper BackboneĢx R7800 - Gateway & WiFi & 3xWireGuard - DDWRT r51887 Std Just a note about my_user_name, if it is your email address eg. That's a good workaround, if used disable GUI DDNS. I also added the command to my startup commands (minus the cron numerics).įeel free to close and reopen and add your findings It seems that In-a-Dyn might need to be updated ( current version is 2.7, and DD-WRT is on 1.96) and https will need to be used.Īs a workaround, I've added this command to my cron:Ġ 0 * * 0 /usr/bin/curl -k -silent -u "my_user_name:my_password" "" >/dev/null 2>&1 Yes, I've tried that, and I still get the same error. Have you tried to change http: to https: in the URL? Check usr,pass,hostname! (HTTP/1.0 301 Moved Permanently Wed Aug 5 19:25:08 2020: W:INADYN: Error validating DYNDNS svr answer. Was working fine for several years until a couple of weeks ago. Last edited by siege on Mon 22:43 edited 1 time in total Thu Jul 30 13:21:26 2020: W:INADYN: Error validating DYNDNS svr answer. Thu Jul 30 13:21:25 2020: I:INADYN: IP address for alias '' needs update to '50.' Thu Jul 30 13:21:24 2020: INADYN: Started 'INADYN Advanced version 1.96-ADV' - dynamic DNS updater. My setup is attached and the specific results I'm seeing now are as follows: I've had a stable setup for years using OpenDNS' DNS-O-Matic service, but in the last week or so something has changed and is now causing an error. Something is going on with the DDNS updater. Posted: Thu 18:41 Post subject: DDNS updater error with OpenDNS/DNS-O-Matic
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |