Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    I cannot get Dynamic DNS

    Scheduled Pinned Locked Moved General pfSense Questions
    10 Posts 4 Posters 202 Views 3 Watching
    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.
    • B Offline
      BlazeStar
      last edited by BlazeStar

      Config:
      Service Type: No-IP
      Interface to monitor: WAN
      Check IP Mode: Always use the Check Ip Service.
      Hostname, username and password are correct (triple checked)
      I enabled verbose logs.

      Then for Check UP Services I have only one enabled:
      https://checkip.amazonaws.com/

      In system logs I see:

      Apr 29 14:34:56	check_reload_status	517	Syncing firewall
      Apr 29 14:34:56	php-fpm	67754	/services_dyndns_edit.php: Dynamic DNS: updatedns() starting
      Apr 29 14:34:56	php-fpm	67754	/services_dyndns_edit.php: Dynamic DNS (XXX) There was an error trying to determine the public IP for interface - wan (pppoe0 ).
      

      Same config was working before, now it's not working anymore.

      Changed password, changed check IP service, checked everything, can't get it to work.

      plz help

      E patient0P 2 Replies Last reply Reply Quote 0
      • E Offline
        elvisimprsntr @BlazeStar
        last edited by elvisimprsntr

        @BlazeStar

        No-IP switched from username/password to DDNS keys

        https://www.noip.com/support/knowledgebase/how-to-setup-and-use-a-ddns-key

        I use the default Check IP Service

        http://checkip.dyndns.org

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          BlazeStar @elvisimprsntr
          last edited by

          @elvisimprsntr thanks but what the logs show is that pfSense can't even fetch my public IP.

          So the problem is not with NO-IP, I believe.

          E 1 Reply Last reply Reply Quote 0
          • E Offline
            elvisimprsntr @BlazeStar
            last edited by

            @BlazeStar

            You have to create a DDNS key on No-IP, then configure pfSense DDNS to use those keys

            chpalmerC 1 Reply Last reply Reply Quote 0
            • chpalmerC Offline
              chpalmer @elvisimprsntr
              last edited by

              @elvisimprsntr said in I cannot get Dynamic DNS:

              @BlazeStar

              You have to create a DDNS key on No-IP, then configure pfSense DDNS to use those keys

              Interesting.. I have not set up a key and have used No-IP for years. Still working right now.

              Guess I need to look up your link.

              Triggering snowflakes one by one..
              Primary- Intel(R) Pentium(R) CPU G4400 @ 3.30GHz on an M470 WG box. pfSense+
              Lab Unit- Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box. pfSense CE 2.8.1

              E 1 Reply Last reply Reply Quote 0
              • E Offline
                elvisimprsntr @chpalmer
                last edited by elvisimprsntr

                @chpalmer

                I should say, No-IP switched to DDNS keys for paid domains.

                Are you using a free No-IP DDNS domain or paid?

                B chpalmerC 2 Replies Last reply Reply Quote 0
                • B Offline
                  BlazeStar @elvisimprsntr
                  last edited by

                  @elvisimprsntr said in I cannot get Dynamic DNS:

                  @chpalmer

                  I should say, No-IP switched to DDNS keys for paid domains.

                  Are you using a free DDNS domain or paid?

                  Yes I have a paid domain.

                  Yes I have a DDNS key and it is configured in pfSense.

                  I'm still getting that error and can't update the IP.

                  I believe it has something to do with the fact that my connexion is PPPoE but I don't understand why it should matter since I have a Check IP Service enabled.

                  1 Reply Last reply Reply Quote 0
                  • chpalmerC Offline
                    chpalmer @elvisimprsntr
                    last edited by

                    @elvisimprsntr said in I cannot get Dynamic DNS:

                    @chpalmer

                    Are you using a free No-IP DDNS domain or paid?

                    Paid. I have a few domains through them.

                    Triggering snowflakes one by one..
                    Primary- Intel(R) Pentium(R) CPU G4400 @ 3.30GHz on an M470 WG box. pfSense+
                    Lab Unit- Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box. pfSense CE 2.8.1

                    1 Reply Last reply Reply Quote 0
                    • E Offline
                      elvisimprsntr
                      last edited by elvisimprsntr

                      I think the old username and password method still works, it’s just less secure since it uses your domain credentials. Not good OPSEC.

                      No-IP is encouraging people to use DDNS keys.

                      I left Check IP Mode set to default since pfsense has public IP from my ATT modem in IP passthrough mode.

                      005d926f-6e58-4063-a187-0d55c6bf761f-image.jpeg

                      1 Reply Last reply Reply Quote 0
                      • patient0P Online
                        patient0 @BlazeStar
                        last edited by

                        @BlazeStar is your WAN marked as up in the 'Gateways' widget or under 'Status / Gateways'?

                        In the past people ran into similar issues when pfSense gateway monitoring thinks that the gateway is down.

                        And additionally: what monitoring IP is set for the WAN interface (System / Routing / Gateway)? Sometimes you can't use the ISPs gateway IP for monitoring of PPPoE connections since this IP is not ping-able. You would have to use another public IP, like 1.1.1.1 or 8.8.8.8 or 9.9.9.9.

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