Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Does NameCheap dyndns work for anyone?

    Scheduled Pinned Locked Moved General pfSense Questions
    15 Posts 3 Posters 6.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • jimpJ
      jimp Rebel Alliance Developer Netgate
      last edited by

      I don't use wildcard though - perhaps their URL format changed for wildcard.

      Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      1 Reply Last reply Reply Quote 0
      • T
        torontob
        last edited by

        I have unchecked wildcard and used 2.0.2 development version and still the same error. Can someone else please confirm this?
        Also, what exactly am I supposed to do on namecheap portal with the domain?

        Thanks

        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          On Namecheap you have to go into your DNS options and enable Dynamic DNS and some other bits. It's all in their FAQ. You'll get a long/random key and that is the "password" used in the GUI.

          http://www.namecheap.com/support/knowledgebase/article.aspx/36/11/what-should-i-do-in-order-to-start-using-dynamic-dns

          Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          1 Reply Last reply Reply Quote 0
          • T
            torontob
            last edited by

            I have done exactly the same and I am on 2.1 Development version from April. It is still not working. Clearly, I am doing something wrong on pfSense or Namecheap side. Can you please advise how I can diagnose the issue? What else is there for me to look at other than the System logs?

            Thanks

            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

              On 2.1, edit the Namecheap DDNS entry and check the box to enable verbose logging.

              Also try manually updating it using the format they show here:

              http://www.namecheap.com/support/knowledgebase/article.aspx/29/

              If that doesn't work either, it's probably your account or settings on Namecheap. If it does work, then it may be something in pfsense yet.

              Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

              1 Reply Last reply Reply Quote 0
              • T
                torontob
                last edited by

                Thanks again Jim. I am trying to work a version 2.0.1 one. The 2.1 Developmental works now but I can't afford to update all pfSense boxes now. It's probably an easy breezy update of the URL that should get it working for older versions too.

                Per the URL you posted this update link should have been used in pFsense code but I can't see it anywhere on Github pfSense project:

                https://dynamicdns.park-your-domain.com/update?host=[host_name]&domain=[domain.com]&password=[domain_password]&ip=[your_ip]

                Can you please point me to the file responsible for updating NameCheap and I will try to modify it.

                Thanks,

                1 Reply Last reply Reply Quote 0
                • P
                  phil.davis
                  last edited by

                  https://github.com/pfsense/pfsense/blob/master/etc/inc/dyndns.class
                  Line 483 to 499 has a block of Namecheap-specific code.

                  As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                  If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                  1 Reply Last reply Reply Quote 0
                  • T
                    torontob
                    last edited by

                    Is the master branch same as the 2.1 developmental?

                    Thanks a lot

                    1 Reply Last reply Reply Quote 0
                    • T
                      torontob
                      last edited by

                      All right so this is a really easy fix for prior version. A variable name is wrong and can be fixed by following:

                      Edit the file /etc/inc/dyndns.class and change to $dnspass for password variable like this:

                      $server = "https://dynamicdns.park-your-domain.com/update?host={$hostname}&domain={$domain}&password={$dnspass}&ip={$this->_dnsIP}";
                      
                      1 Reply Last reply Reply Quote 0
                      • P
                        phil.davis
                        last edited by

                        Look at this commit: https://github.com/pfsense/pfsense/commit/4178d033a22655b8494f013cf2d2e6566deef692
                        You will want to apply all the changes (3 lines) to the corresponding places in the 2.0.3 version.
                        If that change makes it work, then it seems like you have some white space before or after your password?

                        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                        1 Reply Last reply Reply Quote 0
                        • T
                          torontob
                          last edited by

                          @phil.davis:

                          Look at this commit: https://github.com/pfsense/pfsense/commit/4178d033a22655b8494f013cf2d2e6566deef692
                          You will want to apply all the changes (3 lines) to the corresponding places in the 2.0.3 version.
                          If that change makes it work, then it seems like you have some white space before or after your password?

                          Thanks phil. All the three lines you mentioned are needed in order for the IP to update properly.

                          1 Reply Last reply Reply Quote 0
                          • jimpJ
                            jimp Rebel Alliance Developer Netgate
                            last edited by

                            Then you most certainly have some unintended whitespace before or after your password in the GUI.

                            e.g. " mypass" or " mypass " or "mypass "

                            Probably copied and pasted from the Namecheap site accidentally.

                            Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                            Need help fast? Netgate Global Support!

                            Do not Chat/PM for help!

                            1 Reply Last reply Reply Quote 0
                            • T
                              torontob
                              last edited by

                              BANG ON! darn it. What a waste of time. The pass from NameCheap portal was suffixing a white space. It seems like all the code update I did is waste now :(

                              Thanks a lot though everyone!

                              1 Reply Last reply Reply Quote 0
                              • GertjanG Gertjan referenced this topic on
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.