ddclient nohost error

[georg3otj]

Hi,

I'm using ddlclient to update dynamic public ip to dnsomatic. 
I'm confused that when i tried :

https://updates.dnsomatic.com/nic/update?hostname=laxo-mdn 
response is = good 180.241.96.217

but when i checked ddclient log :

Jun 30 12:16:50 thundercats ddclient[6164]: RECEIVE: nohost 
Jun 30 12:16:50 thundercats ddclient[6164]: FAILED: updating laxo-mdn: nohost: The hostname specified does not exist in the database

/etc/ddclient.conf content is as follow :

ssl=yes 
syslog=yes 
verbose=yes 
daemon=300 
use=web, web=myip.dnsomatic.com 
server=updates.opendns.com 
protocol=dyndns2 
login=xxxxxxxxx@xxxxxxxxxxxxxx 
password=xxxxxxxxxx 
laxo-mdn

I've tried to search for hints and clues but nothing helps so far. 
Please help.

Thank you.

[rotblitz]

You currently do not update through DNS-O-Matic, but directly to OpenDNS, as seen from

   server=updates.opendns.com

If you want to update through DNS-O-Matic, then this line should look like this:

   server=updates.dnsomatic.com

However, you also can update directly to OpenDNS as you do.  It is not required to go through DNS-O-Matic.

Regarding the "nohost" return code, it looks like the network label of your OpenDNS dashboard network at https://dashboard.opendns.com/settings/ is not exactly laxo-mdn, else OpenDNS would not return "nohost".  Network labels are strictly case-sensitive.

[georg3otj]

Ah yes, now it makes sense, i tried to change server param to  server=updates.dnsomatic.com and it works !

Jun 30 20:21:37 thundercats ddclient[13466]: RECEIVE: good 180.241.96.217
Jun 30 20:21:37 thundercats ddclient[13466]: SUCCESS: updating laxo-mdn: good: IP address set to 180.241.96.217

now that the update goes thru dnsomatic, did opendns aware of this and it just works ?

As your info that i can update directly to opendns and if i want to do that, 

use=web, web=myip.dnsomatic.com  >> do i need to change this to maybe xxx.opendns.com ? 

about the nohost return code, i am sure that the network label at opendns dashboard and ddclient.conf is the same "laxo-mdn" but somehow it didn't go through, and i still got nohost when using param server=updates.opendns.com

Thanks rotblitz 

[georg3otj]

i forgot to info that i did delete and re-create the network label "laxo-mdn" just to be sure, but even after that, i still got the nohost return code

Thanks rotblitz

[rotblitz]

"now that the update goes thru dnsomatic, did opendns aware of this and it just works ?"

You either visit https://dashboard.opendns.com/settings/ (the IP address should be in bold), or you visit https://www.dnsomatic.com/ and click the log icon beside the OpenDNS service.

"use=web, web=myip.dnsomatic.com  >> do i need to change this to maybe xxx.opendns.com ?"

No.

"i still got the nohost return code"

No idea why this is.  Check with a web search for related reports in Linux or ddclient forums.  There are many.

[georg3otj]

I think i found out but please confirm if it is what i think it is.

originally i config 2 network (with 2 network label) at an account, which are laxo-mdn and laxo-pst.

laxo-mdn got nohost return code, while laxo-pst run smooth, both using same ddclient.conf (difference just network label) on same one opendns account.

just now i tried to create a new account just for laxo-mdn, and it just works beautifully.

so i basically create an account for each network and it runs well.

Thanks rotblitz

[rotblitz]

"both using same ddclient.conf"

I do not think that ddclient can update more than one item at one account.  You would need to run another ddclient instance to do that, possibly on another device.

Especially for OpenDNS, you cannot have two OpenDNS dashboard networks with the same IP address registered.  An IP address can be registered only once at OpenDNS or Umbrella, globally.

[georg3otj]

I am sorry if i wrote poorly that leads to misunderstanding

Just to clarify :

I got two linux servers at two location, with different public ip address

Both linux server runs its own ddclient, with the same configuration, and the difference just network label, as one is laxo-mdn and the other is laxo-pst

Both ddclient.conf use the same login and password, so only one opendns account for two ddclient on two linux servers

The condition above leads to one ddclient works well (laxo-pst) and the other got nohost return code (laxo-mdn)

I then create a new opendns account especially for laxo-mdn, and so each ddclient use its own opendns account, and now both ddclient at both servers runs well.

CMIIW, the above conditions let me came to conclusion that an opendns account could not be used for more than one ddclient instance.

[rotblitz]

This makes sense.  It may be a limitation or a glitch in the OpenDNS system.  To get it verified you could open a support ticket.  I would have expected that it works the way you did it.

[georg3otj]

I will open a support ticket and hopefully get a clear answer, will post the updates here if there is any.

Thanks rotblitz