Does the Dynamic DNS updater create a log file anywhere? I'm having trouble getting the Custom URL service to work with dnspark.net. I believe it has to go through an SSL connection. Does tomato support https for the Custom URL?
Date: 22 Oct 2010 07:52
Number of posts: 7
RSS: New posts
Yes, it supports https as long as the custom URL starts with "https://".
It doesn't write the log, but the error message - if there was an error - is displayed on the Basic->DDNS page as "Last Result".
To get more detailed diagnostic info with complete request and response, set "debug_ddns" nvram variable:
nvram set debug_ddns=1
After failed DDNS update attempt, check the /tmp/mdu-<ddns_service_name>.txt file - it will contain the info you're looking for.
Thanks for your help. The URL does start with https://. Here is the URL I am using, with some obvious modifications:
That should work right? When I try it through a webbrowser it does work, but when I try it through Tomato's ddns, i get the following on the Basic->DDNS page as the Last Result:
Unknown error (-1).
I sshed into the router and typed:
nvram set debug_ddns=1
and then I forced the next ddns update and get the same error. (By the way I checked and it really isn't getting updated, unlike when I do it through a browser)
I tried to look for the log file but this is all I see under the /tmp directory:
root@router:/tmp/home/root# ls /tmp
etc home mnt share var
Any more ideas?
Oh, by the way I am using v1.28.9052 MIPSR2-beta23 K26 USB vpn3.6 on an ASUS RT-N16 router
Another update, I am using to DDNS services OpenDNS as well as DNSPark. When I force a OpenDNS update, I do get the logfile in the /tmp directory for that update. However none is created for my DNSPark Custom URL update.
Okay, so I never was able to get it to update DNSPark, I really do think it's an ssl issue, it doesn't seem to be authenticating properly. But anyways, I decided to just use DNS-O-Matic to update all my DDNS services and that works well.
It's indeed ssl issue - however, it seems to be DNSPark that does something weird/non-standard.
Tomato uses MatrixSSL library for SSL support, but I also tested it with PolarSSL and the latest OpenSSL 1.0.0a - and with DNSPark it's always failing during SSL handshake stage, no matter what library I'm using. This is the only service that fails - all other Tomato supported DDNS services that use SSL (DDNS, Dnsomatic, HE, etc) work fine. I'm not an SSL expert, but it does seem to me that DNSPark has some extra requirements not clearly described on their site…
I just wanted to suggest using DNS-O-Matic, but I see you already found out about this option…