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

(SOLVED) Dynamic DNS stop updating NO-IP but from pfsense status is updated

DHCP and DNS
16
32
21.9k
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.
  • S
    SipriusPT
    last edited by SipriusPT Mar 28, 2021, 9:05 PM Mar 28, 2021, 8:11 PM

    Hello everyone,

    Without any error or warning, my no-ip free dns stop being updated. I've being use it for the pass 3 or 4 years, but this year I notice that was no longer being updated.

    From pfsense seems to be alright:

    64465240-8866-4ddd-90dc-6385bacf58d8-image.png

    From NO-IP side, I only had the last IP that I've added manually, a week ago, when I notice that this was happening:

    9311e34f-959c-46f9-9d03-80a009dd4b97-image.png

    From pfsense system log:

    143d55cb-a7ee-4045-bd85-e1c524c54c90-image.png

    Where it says that the IP didnt changed in last 25 days, but that is not true.

    I've already tried to force update and reboot pfsense but no changes.

    I had this issue on 2.4.5-p1, so I tried to upgrade to 2.5.0 but same thing.

    Anyone is having this issue?

    1xSG-4860-1U
    1xSG-3100
    2xpfSense Virtual Machines

    G A 2 Replies Last reply Mar 28, 2021, 8:42 PM Reply Quote 0
    • G
      gabacho4 Rebel Alliance @SipriusPT
      last edited by Mar 28, 2021, 8:42 PM

      @sipriuspt I had this happen but chalked it up to a fluke. I was only able to get it to work again by deleting the ddns client info and then setting it up again.

      S 1 Reply Last reply Mar 28, 2021, 9:04 PM Reply Quote 1
      • S
        SipriusPT @gabacho4
        last edited by Mar 28, 2021, 9:04 PM

        @gabacho4 Thanks a lot for the help, it works!

        I've simply copy that client, and saved, then deleted the previous one, and enable the new one, and that dynamic DNS was again updated.

        I was starting to expect that there was some changes on no-ip service, instead of a issue on pfsense side.

        1xSG-4860-1U
        1xSG-3100
        2xpfSense Virtual Machines

        G 1 Reply Last reply Mar 28, 2021, 9:06 PM Reply Quote 0
        • G
          gabacho4 Rebel Alliance @SipriusPT
          last edited by Mar 28, 2021, 9:06 PM

          @sipriuspt Sweat deal! My guess is that something in the config gets messed up in the upgrade to 2.5/21.02. Very glad you're back in your way!

          1 Reply Last reply Reply Quote 1
          • R
            redtech116
            last edited by Apr 8, 2021, 12:41 AM

            Having a similar issue with NOIP groups not updating.
            everything in pfsense says it's working, but not on the noip side when assigning a hostname to a group and setting a password for the group
            username = groupname:username
            & change the password to the group password
            tried about every combo of resetting up..no luck.

            G 1 Reply Last reply Apr 8, 2021, 4:09 AM Reply Quote 0
            • G
              gabacho4 Rebel Alliance @redtech116
              last edited by Apr 8, 2021, 4:09 AM

              @redtech116 what do your logs show, if anything?

              R 1 Reply Last reply Apr 8, 2021, 6:53 PM Reply Quote 0
              • R
                redtech116 @gabacho4
                last edited by redtech116 Apr 8, 2021, 6:53 PM Apr 8, 2021, 6:53 PM

                @gabacho4
                When checking the box for Verbose Logging I see the following
                /services_dyndns_edit.php: Response Data: badauth\x0d
                or
                /services_dyndns_edit.php: Response Data: nochg (ipaddress)\x0d

                trying different username combos no change
                group:username
                group:email
                changing passwords etc..
                something with the group name pfsense probably the ':' just not happy..

                O 1 Reply Last reply Jun 4, 2021, 4:55 PM Reply Quote 0
                • O
                  ohbobva @redtech116
                  last edited by Jun 4, 2021, 4:55 PM

                  I don't think this is solved.

                  It works on 2.4.4-RELEASE-p3 but something in the way it's encoding the username/password is apparently broken on 21.05.

                  I'm holding off on upgrading several units due to this, and holding off on a new install with 21.05 as well.

                  J 1 Reply Last reply Jun 4, 2021, 11:00 PM Reply Quote 0
                  • J
                    jiunnyik
                    last edited by Jun 4, 2021, 10:57 PM

                    My Dynamic DNS stop updating NO-IP too for VLAN 500 PPPOE interface.

                    I have pfsense 2.5.1 community edition, default WAN interface is set as null, and Internet Connection is made through VLAN 500 PPPOE interface. I'm from Malaysia, my ISP is TM provide Unifi fiber connection.

                    After I set up Dynamic DNS, NO-IP on this machine, its status show updated, however NO-IP website hostname is updated.

                    I tested another machine B, pfsense 2.5.1 community edition, with default WAN DHCP, Dynamic DNS is updating NO-IP.

                    Can advice on this? Thank you.

                    O 1 Reply Last reply Jun 5, 2021, 3:47 AM Reply Quote 0
                    • J
                      jiunnyik @ohbobva
                      last edited by Jun 4, 2021, 11:00 PM

                      @ohbobva you have pfsense+ ? I have 1 unit SG-5100, updated to pfsense+ 21.05, Dynamic DNS is updating NO-IP.

                      1 Reply Last reply Reply Quote 0
                      • O
                        ohbobva @jiunnyik
                        last edited by Jun 5, 2021, 3:47 AM

                        @jiunnyik Do you use the group feature of NO-IP?

                        If so, in your Dynamic DNS settings of PFsense, what is the format of your NO-IP username?

                        All of my PFSense units have been configured, for years, using the following format, which was the correct format at the time they were configured (and is still valid to NO-IP):

                        groupname:myemail@example.com
                        

                        Something has changed in the latest versions of PFsense that appears to prevent this previously working format from working. Maybe the encoding is different. Maybe someone can go back and see how the username was encoded in the previous working versions of PFsense.

                        This should be fixed by Netgate so that already deployed units using NO-IP Dynamic DNS, that upgrade to the latest PFSense, don't stop working unexpectedly. NO-IP has documentation on integration with routers.

                        However, a workaround, which only works on the newer version of PFsense, is to change the username format to be:

                        groupname#username
                        

                        Note: The NO-IP "username" is different from the NO-IP email address that was previously what you used for the username.

                        J 4 1 3 Replies Last reply Jun 5, 2021, 4:16 AM Reply Quote 1
                        • J
                          jiunnyik @ohbobva
                          last edited by Jun 5, 2021, 4:16 AM

                          @ohbobva nope, I'm not using the group feature of NO-IP.

                          In Dynamic DNS settings of pfSense, the username is my name jiunnyik, which I use to login noip.com

                          I bet this is correct settings, as I tested on other two machines with WAN DHCP mode, it can update NO-IP. One machine is pfsense 2.5.1, while the other one machine is Netgate SG-5100 with pfsense+ 21.05

                          The machine that unable update no-ip is on VLAN PPPOE interface, not sure is this cause unable update no-ip.

                          1 Reply Last reply Reply Quote 0
                          • 2
                            2lostkiwis
                            last edited by 2lostkiwis Jun 22, 2021, 3:30 AM Jun 22, 2021, 3:28 AM

                            I came across this post as one of my clients stopped auto updating... from pure guesswork I found the following:

                            The the one that stopped updating was running pfsense+ 21.05 while the others were using the community version. For some unknown reason the pfsense+ needs to log in with the username while the community version needs to log in with the email address.

                            It used to work so it seems at some point when upgrading the pfsense+ version it changed and at that point stopped updating.

                            J 1 Reply Last reply Jun 22, 2021, 3:49 AM Reply Quote 1
                            • J
                              jiunnyik @2lostkiwis
                              last edited by Jun 22, 2021, 3:49 AM

                              @2lostkiwis said in (SOLVED) Dynamic DNS stop updating NO-IP but from pfsense status is updated:

                              I came across this post as one of my clients stopped auto updating... from pure guesswork I found the following:

                              The the one that stopped updating was running pfsense+ 21.05 while the others were using the community version. For some unknown reason the pfsense+ needs to log in with the username while the community version needs to log in with the email address.

                              It used to work so it seems at some point when upgrading the pfsense+ version it changed and at that point stopped updating.

                              I tried with your suggestion, log in with email address, but still no luck. It won't work. I tested on pfsense community edition, 2.5.1

                              1 Reply Last reply Reply Quote 0
                              • A
                                AlexanderK
                                last edited by Jul 7, 2021, 5:37 PM

                                i updated today to 2.5.2 and this issue occurred. Really strange.
                                The solution with grouname#email@email.com seems to working on pfsense gui but not updating no-ip application.
                                Really strange situation

                                1 Reply Last reply Reply Quote 0
                                • S
                                  s25a
                                  last edited by Aug 12, 2021, 9:13 AM

                                  Hi,

                                  I updated to release 21.05_1 today. Was on an old 2.4.5 before. The NOIP service defintely worked before as i can this in the logfiles in NOIP. After the Update I had to renew the client in PFSENSE and now see Status green with the current IP-Adresse.

                                  However no update on NO-IP side. I tried the workaround by using:

                                  groupname:Username
                                  groupname#Username

                                  Both with Username as only the name and USername as the email adress. No Luck. It does not update.

                                  I can test for you and also provide log files...however please help as I am not an expert on this and need some guidance :-)

                                  Thanks S

                                  G 1 Reply Last reply Aug 17, 2021, 8:07 AM Reply Quote 0
                                  • G
                                    gguglielmi @s25a
                                    last edited by Aug 17, 2021, 8:07 AM

                                    @s25a you can check here:
                                    https://forum.netgate.com/post/987030
                                    This solved the issue for me!

                                    1 Reply Last reply Reply Quote 0
                                    • 4
                                      4ROMANY @ohbobva
                                      last edited by Sep 2, 2021, 6:07 PM

                                      @ohbobva

                                      After I changed my username in PFSENSE FROM my email address to the userid I should have been using DDNS started working immediately. You can log into the no-ip website with either your email or userid - but apparently the DDNS update function needs to use your userid. Thanks ohbobva!

                                      R 1 Reply Last reply Oct 13, 2021, 4:53 PM Reply Quote 1
                                      • R
                                        Remember @4ROMANY
                                        last edited by Oct 13, 2021, 4:53 PM

                                        @4romany Dang, that was it !!!! Thanks!

                                        1 Reply Last reply Reply Quote 0
                                        • A
                                          aesclama @SipriusPT
                                          last edited by Jan 12, 2022, 4:49 AM

                                          @sipriuspt See: https://redmine.pfsense.org/issues/12021

                                          This fixed it for me.

                                          There is no need to urlencode user credentials (CURLOPT_USERPWD already encodes them):

                                          In /etc/inc/dyndns.class edit line 578

                                          from this:

                                          curl_setopt($ch, CURLOPT_USERPWD, urlencode($this->_dnsUser) . ':' . urlencode($this->_dnsPass));
                                          

                                          to this:

                                          curl_setopt($ch, CURLOPT_USERPWD, $this->_dnsUser . ':' . $this->_dnsPass);
                                          
                                          1 Reply Last reply Reply Quote 2
                                          • S sub2010 referenced this topic on Jan 16, 2022, 8:49 PM
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.