IPCOP and dyndns.org custom domains a solution

Maybe some of you tried to configure IPcop to update your domain with dyndns.org's custom dns accounts and noticed that it's just impossible to update you yourdomain.com since the IPcop Dynamic DNS web interface just don't accept an empty HOST field.

After many experimentation I finaly found the solution. You will have to comment a line in your IPcop DDNS script using WinSCP (or any other clients) find the file /home/httpd/cgi-bin/ddns.cgi on IPcop and comment the following line (put a # in front of it):

unless ($cgiparams{'DOMAIN'} =~ /[.]/) { $errormessage = $tr{'invalid domain name'}; }

now your IPcop web interface will accept a DOMAIN name without a "."

exemple for yourdomain.com : in your IPcop dynamic dns web interface enter :

service: dyndns-custom host: yourdomain domain: com user: your username pass: your password enable wildcards : Y

NOW IPCOP will be able to update your custom domain yourdomain.com !

Maybe some of you tried to configure IPcop's Dynamic DNS updater to update your dyndns.org custom DNS domain yourdomain.com and noticed that it's just impossible to do since IPcop's Dynamic DNS web interface just don't accept an empty HOST field.

After many experimentations I finaly found a solution. You will have to edit your IPcop Dynamic DNS script file to accept a DOMAIN field without a ".". Use WinSCP (or any clients) and find the file /home/httpd/cgi-bin/ddns.cgi and comment the following line (put a # sign in front of it) :

unless ($cgiparams{'DOMAIN'} =~ /[.]/) { $errormessage = $tr{'invalid domain name'}; }

Now the IPcop web interface will accept a DOMAIN field without a "."

Exemple to configure yourdomain.com : In the IPcop DDNS web interface enter: SERVICE: dyndns-custom HOST: yourdomain DOMAIN: com USER: your username PASS: your password ENABLE WILDCARDS: Y

Now IPcop will be able to update yourdomain.com