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

    Dyndns update use public ip

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 2 Posters 284 Views 2 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.
    • S Offline
      serbus
      last edited by

      Hello!

      I have an ethernet lte modem connected to a pfsense wan interface and it receives a public ip (25.72.x.x).
      The src ip that is seen by a server on the internet is a different public ip (172.58.x.x).
      The pfsense dyndns update service registers the 25.72.x.x interface address with the dyndns provider, but I would like to have the public ip (172.58.x.x) registered.
      The pfsense default checkip service (checkip.dyndns.org) returns the 172.58.x.x address, but it is not called or used by the dyndns update process unless the wan interface ip is a private address.
      Is there a way to force the pfsense dyndns update process to use the public ip?
      Are there any dyndns service providers that will use the client src ip for the update instead of what is in the url/payload?

      John

      Lex parsimoniae

      1 Reply Last reply Reply Quote 0
      • stephenw10S Online
        stephenw10 Netgate Administrator
        last edited by

        Hmm. Yes I believe there are a number of providers who will just use the source IP of an update. The customer option there may also work rather than using one of the built in presets.

        The pfSense update client will do that anyway if the monitored interface has a private IP but that makes it tricky in your case....

        Steve

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