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

    Dynamic DNS & Namecheap

    DHCP and DNS
    17
    40
    20.3k
    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.
    • Z
      Zoltrix @Gertjan
      last edited by

      Thanks Jangert

      1 Reply Last reply Reply Quote 0
      • J
        jamesg246 @Gertjan
        last edited by

        @gertjan Also experiencing this. If you use the namecheap http update method, then you do get a green tick in the gui. As its been said above, the ip address still updates.

        Z 1 Reply Last reply Reply Quote 1
        • Z
          Zoltrix @jamesg246
          last edited by

          we should enter a bug report I guess

          GertjanG 1 Reply Last reply Reply Quote 0
          • GertjanG
            Gertjan @Zoltrix
            last edited by Gertjan

            @zoltrix said in Dynamic DNS & Namecheap:

            we should enter a bug report I guess

            Some one - here on this forum, or on reddit, wrote that the namecheap support has confirmed the issue, as 'something' on their side was changed (not pfSense, we use all the same version / scripts ) and that they, namecheap, will correct it.

            For the record, as the brand of the company implies, they do not have a huge budget, so this will take some time.
            In the future, they will correct he issue on their side, and everything will be fine again.
            For the time being, a work around exists.

            If pfSense get patched now, and namecheap correct the issue afterwards, the problem will re start all over again, and the patch has to be removed by updating pfSense again.

            edit : Btw : if a bug report has to be opened : go head : good idea. But use the namecheap bug reporter @namecheap - if they have one ....

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            Z 1 Reply Last reply Reply Quote 0
            • Z
              Zoltrix @Gertjan
              last edited by Zoltrix

              @gertjan said in Dynamic DNS & Namecheap:

              For the record, as the brand of the company implies, they do not have a huge budget, so this will take some time.

              Maybe done some homework first.

              Namecheap had over $200 million in revenue in 2020, which was up 35%, or $51.6 million, over the $149 million it posted in 2019.

              It has 11 million registered users and 10 million domains.

              johnpozJ 1 Reply Last reply Reply Quote 0
              • johnpozJ
                johnpoz LAYER 8 Global Moderator @Zoltrix
                last edited by johnpoz

                @zoltrix I think that was meant as joke ;)

                But they could have 1 Billion in revenue, doesn't mean they spend any of that on development ;)

                The issue comes down to, if pfsense didn't change anything, and it stopped working because namecheap did change something. Do you also change pfsense to accommodate whatever changed (can you even?), or is namecheap going to change/fix what they did or forget to add or whatever.

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.7.2, 24.11

                GertjanG 1 Reply Last reply Reply Quote 0
                • GertjanG
                  Gertjan @johnpoz
                  last edited by

                  @johnpoz said in Dynamic DNS & Namecheap:

                  I think that was meant as joke

                  Yeah, hope so.

                  @zoltrix said in Dynamic DNS & Namecheap:

                  Namecheap had over $200 million in revenue in 2020, which was up 35%, or $51.6 million, over the $149 million it posted in 2019.

                  I didn't fact-check that, but I tend to believe the numbers. I 'know' who namecheap is.
                  They have probably also an 'owner' or share holders, or whatever. And now we reached the point : Who comes first :
                  The 'clients' ?
                  The the share holders ?

                  I'm pretty sure, if some one at namecheap sits down for one hour or so, the issue will be solved. One hour !
                  But noooop - xx thousand of clients will have to wait for weeks - now months.

                  Btw : I say up front : I have nothing against namecheap - neither against the concept as companies and how they work and their goals. I'm working for a company - and the idea is mainly : making € (no $ here).
                  And making fun, of course.

                  And also : again :
                  They have confirmed : they introduce the issue.
                  They fix it.
                  Or they shall feel the power of Free DynDNS service.
                  Although that won't touch them financially, as the service is free - and is this might be the actual reason why all this takes so long ;)

                  No "help me" PM's please. Use the forum, the community will thank you.
                  Edit : and where are the logs ??

                  1 Reply Last reply Reply Quote 0
                  • D dma_pf referenced this topic on
                  • D dma_pf referenced this topic on
                  • S
                    SteveITS Galactic Empire @Zoltrix
                    last edited by

                    @zoltrix said in Dynamic DNS & Namecheap:

                    logs show the "/services_dyndns_edit.php: phpDynDNS (XXX): (Unknown Response)" error.

                    https://redmine.pfsense.org/issues/12816

                    There is a patch in the new System Patches 2.0 package. (recommended patches are now listed in it)

                    I do not get the unknown response error when clicking Save and Force Update. I get "(Success) IP Address Updated Successfully!" but 2-3 minutes later the page times out and it logs a " *406 upstream timed out (60: Operation timed out) while reading response header from upstream" error.

                    Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                    When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                    Upvote 👍 helpful posts!

                    T M 3 Replies Last reply Reply Quote 3
                    • T
                      thearamadon @SteveITS
                      last edited by

                      This post is deleted!
                      1 Reply Last reply Reply Quote 0
                      • T
                        thearamadon @SteveITS
                        last edited by

                        @steveits said in Dynamic DNS & Namecheap:

                        @zoltrix said in Dynamic DNS & Namecheap:

                        logs show the "/services_dyndns_edit.php: phpDynDNS (XXX): (Unknown Response)" error.

                        https://redmine.pfsense.org/issues/12816

                        There is a patch in the new System Patches 2.0 package. (recommended patches are now listed in it)

                        I do not get the unknown response error when clicking Save and Force Update. I get "(Success) IP Address Updated Successfully!" but 2-3 minutes later the page times out and it logs a " *406 upstream timed out (60: Operation timed out) while reading response header from upstream" error.

                        This patch doesn't work anymore, but there's an updated one that works here:

                        https://github.com/pfsense/pfsense/commit/70db168b7f7eb4d4e702f965aa4956e93340575f?diff=unified

                        Cloudless Smart HomeC 1 Reply Last reply Reply Quote 5
                        • Cloudless Smart HomeC
                          Cloudless Smart Home @thearamadon
                          last edited by

                          @thearamadon thanks, worked perfect!

                          1 Reply Last reply Reply Quote 2
                          • M
                            mooky1977 @SteveITS
                            last edited by

                            @steveits Can confirm, this fix works for me on pfSense Plus 22.05 to fix my namecheap dynDNS problem.

                            System Patches ID: 70db168b7f7eb4d4e702f965aa4956e93340575f

                            Thanks!

                            Z 1 Reply Last reply Reply Quote 1
                            • Z
                              Zoltrix @mooky1977
                              last edited by

                              @mooky1977 cool, let's hope it gets rolled into the next pfsense release.

                              Cloudless Smart HomeC 1 Reply Last reply Reply Quote 0
                              • Cloudless Smart HomeC
                                Cloudless Smart Home @Zoltrix
                                last edited by Cloudless Smart Home

                                @zoltrix I can guarantee it... https://docs.netgate.com/pfsense/en/latest/releases/23-01.html

                                Z 1 Reply Last reply Reply Quote 2
                                • Z
                                  Zoltrix @Cloudless Smart Home
                                  last edited by

                                  @appleguy awesome!

                                  I guess the original comments by @Gertjan and @johnpoz were off the mark.

                                  1 Reply Last reply Reply Quote 0
                                  • GertjanG
                                    Gertjan
                                    last edited by

                                    @zoltrix said in Dynamic DNS & Namecheap:

                                    off the mark

                                    My point of view :
                                    2020 : namecheap changed the text value when an IP was updated.
                                    Like "IP was accepted" to "IP was changed".
                                    On the pfSense side, the "IP was changed" didn't match as an "Ok" result, so, to be safe, it was treated as an no-ok resulat, the GUI showed a red IP message.
                                    But : surprise : the IP was updated on the namecheap side.
                                    Then, several month later, the returned text values changed again.
                                    To make dyndns namedcheap work again, code had to change again on the pfSense side.
                                    This is just what I could call "development", not really a bug. The results is always : it doesn't work anymore for the end user.
                                    This year, the same thing happened.
                                    A pfSense bug ? Noop, namecheap changed the returned text value again.
                                    Like (example) "From "Ok" to "OK".

                                    Now I have my ideas why they do this.

                                    What I don't get is : no messages on whatever media to explain that something has changed.
                                    And because we are all curious, and some of us even want to learn and understand why things have changed.
                                    But nothing.
                                    Just a confirmation on the namecheap forums, months later : "yep, something changed".

                                    No "help me" PM's please. Use the forum, the community will thank you.
                                    Edit : and where are the logs ??

                                    R 1 Reply Last reply Reply Quote 1
                                    • R
                                      renarde3 @Gertjan
                                      last edited by

                                      Hi @jimp, @johnpoz, @gertjan, thanks for all of your hard work on pfSense! I shudder to think what my world would be like without it.

                                      Question for those of you who use Namecheap for DDNS. Is it possible to use Namecheap Web hosting DNS (aka cPanel) with pfSense DDNS? Or will I need to move my DNS records to Namecheap's BasicDNS to set things up using the instructions @jimp has given above (I suspect the answer is "yes")?

                                      Having created DDNS records in the Namecheap Web hosting DNS's cPanel UI, the records created provide a URL to use for DDNS, not a password. Without passwords it seems I'm at an impasse.

                                      @jamesg246 refers to a "namecheap http update method" in this thread. I suspect I could use this with the cPanel DDNS. Could someone point me at directions for how to set this up?

                                      Or feel free to tell me I'm trying to do the impossible (or silly) and would be wise to take the time and move my DNS records from cPanel to their Basic DNS.

                                      Thanks!

                                      Cloudless Smart HomeC 1 Reply Last reply Reply Quote 0
                                      • Cloudless Smart HomeC
                                        Cloudless Smart Home @renarde3
                                        last edited by Cloudless Smart Home

                                        @renarde3 I just have regular namecheap domain hosting. click on manage, then the advanced dns tab.

                                        https://www.namecheap.com/support/knowledgebase/article.aspx/36/11/how-do-i-start-using-dynamic-dns/

                                        using pfsense+ 22.05, I used the patch refrenced above, but installed 23.01-RC yesterday and removed that and one other patch. all working great!

                                        1 Reply Last reply Reply Quote 0
                                        • R
                                          renarde3
                                          last edited by renarde3

                                          Hi @cloudless-smart-home, thanks for your quick response.

                                          I've successfully set up the DDNS records in the Namecheap Webhosting (aka cPanel) UI, but have not been able to figure out how to use the URLs it generates to communicate with the DDNS clients I have set up in pfSense. That's where I'm getting stuck.

                                          From this image in the Namecheap Domain List, I suspect I need to switch to their BasicDNS (Webhosting DNS) to make this work. I was hoping to get confirmation before I have to recreate my DNS entries.
                                          NamecheapDomainDashboard_20230209.png

                                          Cloudless Smart HomeC 1 Reply Last reply Reply Quote 0
                                          • Cloudless Smart HomeC
                                            Cloudless Smart Home @renarde3
                                            last edited by Cloudless Smart Home

                                            @renarde3
                                            https://www.namecheap.com/support/knowledgebase/article.aspx/36/11/how-do-i-start-using-dynamic-dns/

                                            will walk you through the process. look at the other links on that page too if it's not clear.

                                            https://www.namecheap.com/support/knowledgebase/article.aspx/595/11/how-do-i-enable-dynamic-dns-for-a-domain/

                                            R 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.