Namecheap and duplicate hostnames not working

Help
Glenn Chan
2008-06-25
2014-04-11
  • Glenn Chan
    Glenn Chan
    2008-06-25

    My ddclient.conf looks something like this:

    protocol=namecheap, login=broadcastreferencemonitors.com,\ password=f50192d8373CENSOREDa2e4,test,www,test

    protocol=namecheap, login=glennchan.info,\ password=88D0E89CENSORED9AF1-C816023561B9,www,@

    When I run the program, the second instances of test and www aren't updated.
    debian:/usr/sbin# ddclient -force
    SUCCESS:  updating @: good: IP address set to 99.226.255.3
    SUCCESS:  updating test: good: IP address set to 99.226.255.3
    SUCCESS:  updating www: good: IP address set to 99.226.255.3

    I don't care so much about test, but I would like to be able to update www.broadcastreferencemonitors.com and www.glennchan.info

    How do I do this or is it simply a bug/limitation?

     
    • Glenn Chan
      Glenn Chan
      2008-06-25

      A second issue was that I found the example .conf file misleading/confusing.

      Comments like the following would seem more intituive for me (the password is not real, and I'm not sure if it's supposed to be followed by a comma)
      ##
      ## NameCheap (namecheap.com)
      ## Example for mail.acmewidgets.com
      # protocol=namecheap,                           \ # server=dynamicdns.park-your-domain.com,       \ # login=acmewidgets.com,                 \ # password=12D0E89D-EBE3-15B6-9AF0-C801023561B9            \ # mail

      The current comments suggests settings that don't work.
      ##
      ## NameCheap (namecheap.com)
      ##
      # protocol=namecheap,                           \ # server=dynamicdns.park-your-domain.com,       \ # login=my-namecheap.com-login,                 \ # password=my-namecheap.com-password            \ # myhost.namecheap.com
      The last line would suggest mail.acmewidgets.com... which won't work.

      Any help for the first issue would be greatly appreciated.  Thanks!

       
      • wimpunk
        wimpunk
        2008-06-25

        Did you check the forum about namecheap.  There are some messages out there about how to configure namecheap.  I'll try to take a closer look tonight (CET).

         
        • Glenn Chan
          Glenn Chan
          2008-06-28

          Hi wimpunk,

          Did you get a chance to look at this?

           
          • wimpunk
            wimpunk
            2008-07-03

            I took a quick look but I didn't found any way to create a testing account.  I'm also missing a link to the description of the protocol they are using.  So if you could help me with this one, this issue should get fix faster.

             
            • Glenn Chan
              Glenn Chan
              2008-07-03

              Hi wimpunk,

              Good news!
              All I needed to do was to implement the patch discussed here:
              http://sourceforge.net/forum/message.php?msg_id=4789961

              I assumed incorrectly that the latest version from subversion would have that patch.

              2- To make ddclient a better program, I'd humbly suggest that:

              a- The help file contain examples.  This would've helped me out a lot as I had to tried many different combinations before namecheap would work.  When the help file talks about a password, it's not clear which password it's talking about (your namecheap.com login, or the really long string password for dynamic DNS).  The comments in the .conf file right now assume that the user is familiar with the DNS formats and can therefore figure out which of the two passwords is the one to use.

              So an example for multiple domains with namecheap would be:

              protocol=namecheap,     \ login=acmewidgets.info,     \ password=47c7c61c81f949039865c88f832f733d #your dynamic DNS password, not namecheap.com account password; this password is found under Miscellaneous -->  Dynamic DNS
              www.acmewidgets.info
              subdomain.acmewidgets.info

              protocol=namecheap,     \ login=yourcompany.com,     \ password=12c7c61c81f949039865c88f832f733d
              www.yourcompany.com
              subdomain.yourcompany.com

              By providing an example like that, it

              b- hankkessel's patch is somewhat of a workaround.  I'm glad that it works, but it's not 100% ideal since it's possible for the user to configure ddclient.conf wrong.  e.g. if the conf file looked like
              protocol=namecheap,     \ login=acmewidgets.info,     \ password=47c7c61c81f949039865c88f832f733d
              www
              subdomain

              protocol=namecheap,     \ login=yourcompany.com,     \ password=12c7c61c81f949039865c88f832f733d
              www
              subdomain

              then www.yourcompany.com and subdomain.yourcompany.com wouldn't get updated.

              3- Thanks again for looking into this and for putting in work developing ddclient.

              Cheers.

              Glenn

               
              • wimpunk
                wimpunk
                2008-07-04

                The patch has been added to the patches section (see #2010819) and has been added to the patches directory of ddclient.  I'll apply it while updating the documentation.

                 
      • dcg
        dcg
        2009-04-07

        This was driving me nuts.  The tech support at namecheap does not know what is going on and managed to feed be back incorrect useage for the conf file.

        Just for reference, I updated to ddclient 3.8 and this is the conf file format that is correctly working for me.  It's updating both my host and the domain now...

        # /etc/ddclient.conf
        protocol=namecheap
        use=if, if=eth1
        server=dynamicdns.park-your-domain.com
        login=22returbo.net
        password=1b9aa1865e02<CENSOR>
        host1,www

         
    • Glenn Chan
      Glenn Chan
      2008-06-25

      Hi wimpunk,

      Thanks for the reply.  I took a look at the messages out there and the solution doesn't seem to work for me.

      I tried updating via updating via subversion:
      # $Id: ddclient 96 2008-06-13 20:24:24Z wimpunk $

      The "Patch for namecheap" thread
      http://sourceforge.net/forum/message.php?msg_id=4789961
      suggests that users should put in the host+domain name at the bottom, and that ddclient would strip off the domain name.  This doesn't seem to be the case for me:
      WARNING:  SENT:    http://dynamicdns.park-your-domain.com/update?host=www.broadcastreferencemonitors.com&domain=broadcastreferencemonitors.com&password=f5019CENSOREDe658c4797a2e4&ip=99.226.255.3

      You can see that it's sending host=www.broadcastreferencemonitors.com
      when it should be host=www

      I have problem #2 described in that post.  It's the duplicates that don't work for me.

      Thanks in advance.

       
  • biatch0
    biatch0
    2014-03-14

    Any updates for Namecheap? Patch related downloads give me a 403 or "This forum is private." as per above. Checked the ddclient code and it appears to be as per most recommendations in the forum, but still only the last domain gets updated.

     
  • perpsectoff
    perpsectoff
    2014-04-11

    This is from (K)Ubuntuguide at
    http://ubuntuguide.org/wiki/Dynamic_dns#Other_DDNS_services :

    Using ddclient with Namecheap can be quirky. I needed ddclient
    v. 3.8.1 or later. Subhost names (in both the Namecheap
    settings and the ddclient subhost list) must be single words
    (e.g. "mysubhost"). The ddclient did not successfully update
    subhosts with the same name (e.g. "www" or "mail" or "@") in
    multiple domains in Namecheap.

    The easiest solution is to dynamically update (using ddclient) the "www" field for one domain only (e.g ''myhost1.me''). For all the other domains, use a "CNAME redirect" to point to the ''www.myhost1.me.'' address of the single domain whose "www" field updates dynamically. CNAME redirections change only the destination IP address; the URLs (of the referring subdomains) are kept the same.

    Another alternative is to use unique subdomain names and then forward the ''www'' entry (using a "URL forward") in the Namecheap settings for one host to a subdomain (e.g. the subhost ''main'' in the Namecheap settings, which would correspond of a "URL forward" to ''http://main.myhost1.me'' for the first host's ''www'' entry) and forward the ''www'' entry in the Namecheap settings for the second host to a different subdomain (e.g. the subhost ''home'' in the Namecheap settings, which would correspond of a "URL forward" to ''http://home.myhost2.me'' for the second host's ''www'' entry). This changes the "www" URL to the subdomain's URL, so your server must be able to handle the new URL (through virtual host files/redirects or .htaccess files). This entails a bit more effort than with the first solution.

    Note: It is tempting to try to forward the "www" field of a domain to a dynamically-updating subhost field, but Namecheap does not allow CNAME redirection to a subhost in the same domain.

    It is then easiest to redirect the @ field's setting (in Namecheap) to the www field setting (using a "URL redirect" to ''http://www.myhost1.me''). This changes the URL ''http://myhost1.me'' to ''http://www.myhost1.me'' while redirecting it, for example.

    An alternative is, in the @ field setting, to use a CNAME redirection, e.g. to ''www.myhost1.me.'', which will preserve the ''http://myhost1.me'' URL while redirecting to the IP address specified by the contents of the www field. This latter method must be accomodated by adjusting the appropriate virtual host file on your server to accept both ''http://myhost1.me'' and ''http://www.myhost1.me''.

    Other solutions found online are at:

    http://sourceforge.net/p/ddclient/discussion/399428/thread/187e6520

    http://robertianhawdon.me.uk/2010/09/03/making-ddclient-work-with-multiple-domains-on-namecheap/

     
    Last edit: perpsectoff 2014-04-12