Yesterday with the exact same settings and without putting each individual hostname after 'hostname=' it instantly started working.
DDWRT has been complaining about problems like this before so I'm wondering if its possible that I AM doing everything right, but OpenDNS has some of their settings screwed up.
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Wed Feb 17, 2010 5:06 Post subject:
Since you already have an 'OpenDNS' account, you already have access to dns-o-matic. You might try that service. It is what I use and I have settings that work for it. They are as follows:
This works without fail for me. If you do not want *.hostname.dydns.com (or whatever your hostname is) to resolve, you can change the URL setting and turn the wildcard option off.
I hope this helps. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Well, I've officially given up on using the 'custom' option on DDWRT to try and update it.
Looking at running scripts on an Ubuntu server which takes the update from somewhere like DynDNS and sends it to the server, which in turn sends it to DNSOMATIC who passes it on to OpenDNS.
I've tried Inadyn, DDClient, and numerous router configurations, and none of them have a way to update multiple dynamic IPs through DNSOMATIC and OpenDNS with ONE single account.
Amazing that someone like OpenDNS, despite the numerous requests will just continue to screw over those of us who have more than one IP to look after.
DNSOMATIC comes back in 20 seconds with a 'badauth' error.
Now I'm really confused as it seems like my problem has absolutely nothing to do with the fact that I'm trying to update multiple hosts to multiple addresses.
I have multiple locations with DDWRT routers updating OpenDNS using DNS-O-Matic. You will have to set up (at least) 2 entries in DNS-O-Matic for each location (a OpenDNS entry and a DynDns entry (or whatever dynamic dns update service you are using)). You also will not be able to add an OpenDNS entry until you FIRST add that location on the OpenDNS website. Confusing, I know, but it does indeed work...
My settings are exactly the same...but for some reason it refuses to update.
Just says 'connecting to server.'
Same problem here, with DD-WRT v24-sp2 (11/02/09) std. Here's how I solved it. My OpenDNS password had multiple special characters. I changed it to a simpler alphanumeric password, and now DD-WRT will update my DNS-O-Matic account.
Don't know if it's the reason, or what character exactly is causing issues, but I'd thought could be something to try if your password has indeed special characters, that the update client might not properly encode or escape.
My settings are exactly the same...but for some reason it refuses to update.
Just says 'connecting to server.'
Same problem here, with DD-WRT v24-sp2 (11/02/09) std. Here's how I solved it. My OpenDNS password had multiple special characters. I changed it to a simpler alphanumeric password, and now DD-WRT will update my DNS-O-Matic account.
Don't know if it's the reason, or what character exactly is causing issues, but I'd thought could be something to try if your password has indeed special characters, that the update client might not properly encode or escape.
My password had special characters and numbers and it would not work. Once I changed it to alphabetic only, the update worked. Considering that the underlying architecture for DD-WRT is Linux, special characters have a different meaning under Linux. I suspect that DD-WRT is not escaping those characters which is causing the command to fail.