- This topic is empty.
March 20, 2009 at 1:20 pm #41554jerwebMember
There seams to be a problem with the dynamic dns update client in zeroshell.
I have a costom DynDNS domain olem.org. But i can’t update it since zeroshell client turns olem.org into olem.dyndns.org.
13:54:44 WAN IP=184.108.40.206 olem.dyndns.org= (Update is needed)
13:54:44 Dynamic DNS updating olem.dyndns.org (olemorg)
13:54:44 ==> nohost
13:54:44 ==> A fatal error occurs and the DDNS client is now disabled. Please solve the problem and enable the Dynamic DNS Client.
Tanks by the way for a super Linux router.April 11, 2009 at 6:09 am #47836tekoholicMember
I’m experiencing the same… I use the DynDNS Custom DNS service with my own domain, and I get the same errors. Am looking at the code in scripts now, looking for a solution…
edit: thought I’d found a workaround, but it failed…December 19, 2009 at 10:25 pm #47837mailserverMember
23:22:05 Dynamic DNS updating .opendns (my_name)
23:22:06 ==> nohost
23:22:06 ==> A fatal error occurs and the DDNS client is now disabled. Please solve the problem and enable the Dynamic DNS Client.
Same issue (beta 12)December 22, 2009 at 2:02 pm #47838JCMember
So you need the ability to type in the host, as opposed to choose the ones from the list. seems its setup for the free hosts. perhaps someone could make it a choice between free hosts and custom host [where user types in their custom host]?April 2, 2011 at 7:49 pm #47839PeterleMember
Is this problem solved?
If yes, how to configure?April 14, 2012 at 10:46 am #47840manu69xMember
I got this error
“A fatal error occurs and the DDNS client is now disabled. Please solve the problem and enable the Dynamic DNS Client”
any idea ?January 8, 2013 at 11:04 pm #47841jhregaladoMember
Same error to me ; Open DNS hosts is blank and it seems ddns client not to update properly.January 22, 2013 at 4:21 pm #47842miketheknifeMember
the only solution i saw was to install the opendns update client on one of my internal servers.
i switched to dyndns and that works.
– mikeMarch 28, 2014 at 1:40 am #47843MarceloMember
I had the exact same problem, which I noticed was actually my fault. Instead of using dyndns.biz (which was the domain I actually created my hostname in dyndns, I was using the default, dyndns.org.
When I noticed this and changed to the correct domain I created, it worked.
PS. by the way, it makes sense that the error message “no host” indicates that there was no such host as mine in the domain dyndns.org. Ok, it should be a little bit more verbose 😉
Hope this helps you.
- You must be logged in to reply to this topic.