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

    DynDNS blocked me

    Scheduled Pinned Locked Moved DHCP and DNS
    61 Posts 7 Posters 27.7k 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.
    • R
      rds_correia
      last edited by

      Ok, the same ones that I had already used a couple of days ago.
      Seems like that way the box will update something through the web, right?
      Just wanted to make sure that there were no new commands issued here.
      Hope this gets fixed on newer releases permanently ;)
      Cheers

      pfSense 2.2.4 running on a HP DL385 G5
      WAN bce(4) + LAN em(4) + OPTn em(4) with 10 VLANs + Snort + PPTP VPN soon to be trashed by OVPN

      1 Reply Last reply Reply Quote 0
      • S
        sullrich
        last edited by

        It is fixed on new releases.

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

          Thanks to both of you, then :).

          pfSense 2.2.4 running on a HP DL385 G5
          WAN bce(4) + LAN em(4) + OPTn em(4) with 10 VLANs + Snort + PPTP VPN soon to be trashed by OVPN

          1 Reply Last reply Reply Quote 0
          • J
            Jesse7
            last edited by

            @mickeybyte:

            Yes, the output looks ok, so if you've done this after Scott had updated the files, you'll have the correct versions for dyndns to work smoothly

            And yes, I'm still running fine with dyndns.

            I also find it hard to search through the ticket system to find out if something is fixed in a new release
            It would be nice if there would be a changes.txt file that is updated at each new release stating what has been fixed, updated, added, deleted
            e.g.

            0.96.6:

            • fixed dyndns cachedIP issue
            • updated Intel NIC drivers to version 999.0.2.99stable
            • …

            0.96.4:

            • ...

            MickeyByte

            The discriptions are so vague I find it impossible to spend so long looking through so many entries to see if something is fixed.
            Would be nice for at least the major fixes to be mentioned to stop a few of the questions poping up.

            Someone that can understand the CVS could volenteer to make a changes post? :)  Doesn't have to be the devs

            1 Reply Last reply Reply Quote 0
            • S
              sullrich
              last edited by

              @Jesse7:

              The discriptions are so vague I find it impossible to spend so long looking through so many entries to see if something is fixed.
              Would be nice for at least the major fixes to be mentioned to stop a few of the questions poping up.
              Someone that can understand the CVS could volenteer to make a changes post? :)  Doesn't have to be the devs

              This will change once we release.  Right now we do not have the resources to document every change seperately.

              Sorry!

              1 Reply Last reply Reply Quote 0
              • M
                mickeybyte
                last edited by

                Kind of started to think about the cachedIP thing used in dyndns (yes, it's me again ;D)

                Just making a change request, don't know if that's the right place…
                What if you checked the current WAN IP against the current IP in the DynDNS service in stead of keeping a cachedIP at the firewall?
                Started thinking about this when I manually changed my dyndns IP using the website of dyndns.org to check if it would update, but it didn't because the CachedIP in the firewall was still the same as current WAN IP.
                Don't know if those situatiions happen frequently, but it could!

                Greetz,
                MickeyByte

                1 Reply Last reply Reply Quote 0
                • M
                  mickeybyte
                  last edited by

                  Hi,

                  You probably won't believe it, but I just got mail from DynDNS telling me my hostname is about to expire in 5 days!
                  In the system logs it nicely says each hour: IP not changed and 28 days not passed, so not updating.
                  Had to clean my dyndns.cache file to make it update!

                  Something wit the timestamp in the file? of the script?

                  M.

                  1 Reply Last reply Reply Quote 0
                  • S
                    sullrich
                    last edited by

                    It expires in 30 days?  So that would be 25 days?  So it hasn't quite hit 28 days?

                    1 Reply Last reply Reply Quote 0
                    • M
                      mickeybyte
                      last edited by

                      Well, better make it less than 25 days then in stead of 28, because getting an e-mail that it will expire is not really the type of e-mails I want to get.
                      One thing for sure, it'll take another month to know if it would really update at the 28th day, cause I've forced it right now :-)

                      M.

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

                        I got blocked to. I'm running beta2 and followed the instructions but it says command not found. Do you have that script available for download?

                        Thanks,
                        Tom

                        1 Reply Last reply Reply Quote 0
                        • S
                          sullrich
                          last edited by

                          These problems have been solved for a long time.  Are you sure that you are not running multiple clients?

                          1 Reply Last reply Reply Quote 0
                          • C
                            codegrinder
                            last edited by

                            hopefully these steps will work for the DHS client too. i having the same trouble.

                            *edit nope it doesn't

                            update_file.sh /etc/inc/dyndns.class

                            update_file.sh: Command not found.

                             4 18:28:22 php: /services_dyndns.php: 
                            Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Current Service: dhs 
                            Jan 4 18:28:22 php: /services_dyndns.php: DynDns: DynDns _checkStatus() starting. 
                            Jan 4 18:28:22 php: /services_dyndns.php: Curl errror occured: Couldn't resolve host '{$server}{$port}' 
                            Jan 4 18:28:22 php: /services_dyndns.php: DynDns: DynDns _update() starting. 
                            Jan 4 18:28:22 php: /services_dyndns.php: DynDns: cacheIP != wan_ip. Updating. 
                            Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Cached IP: 0.0.0.0 
                            Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Current WAN IP: *.*.*.* 
                            Jan 4 18:28:22 php: /services_dyndns.php: DynDns: _detectChange() starting. 
                            Jan 4 18:28:22 php: /services_dyndns.php: DynDns: updatedns() starting 
                            Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Running updatedns() 
                            
                            
                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.