8393 questions

9872 answers

15658 comments

14143 members

0 votes
26 views 0 comments
by
NOIP has a feature that permit to create sub-account using GROUPS to update an host using credential different from main account.

I create in my NOIP account a group called "myGroup" that include the host "myhost.mydomain.com"

The main NOIP account has the username: mainAccount

Using a group called  to update DDNS the username for the group must be a join from groupname and username.

In my example =  myGroup:mainAccount

and the password for the group is different form tha mainAccount

The RUT240 not update DDNS if i use the group credential. In the log I read "badauth"

Instead, if I use the mainAccount credential all works fine.

I can't use the mainAccount credential because I need to configure a router of one of my customers and I dont' want that him can read my NOIP credential. Using group credential my customer can't access to my NOIP account, can update the DDNS ONLY.

Could be a firmware bug ?

I update the RUT240 to latest RUT2XX_R_00.01.14.4.

In the previous firmware the no-ip.com provider was not avilable, in the 01.14.4 come back.

I hope the description of issue is clear.

LOG from /var/log/ddns

 202452       : sending real IP to 'no-ip.com'
 202453       : #> /usr/bin/curl -RsS -o /var/run/ddns/myddns.dat --stderr /var/run/ddns/myddns.err --noproxy '*' 'http://<myGroup>:<mainAccount>:<password>@dynupdate.no-ip.com/nic/update?hostname=myhost.mydomain.com&myip=151.43.14.146'
 202453       : 'no-ip.com' answered:
badauth
 

Thanks in advance.

- Pierluigi

Please log in or register to answer this question.