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

Dynamic DNS not functioning properly after a router change

Scheduled Pinned Locked Moved DHCP and DNS
3 Posts 2 Posters 234 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.
  • J
    James92
    last edited by Feb 29, 2024, 1:11 PM

    Hello all, slight noob on the topic here.

    Got an issue with our firewall in that it does not seem to cache our DynDNS IP correctly. The IP it brings forward matches that on the DynDNS site 9 times out of 10, though it is sometimes different (having tried checkip.dyndns.org and checkip.dyndns.com).

    DynDNS (1).png

    The IP shown on the above images matches that on the DynDNS site at the same time:

    DynDNS (2).png

    Occassionally, the IP will show green but as soon as you click onto another page within the PFSense GUI it and then back in it will go red again (note the IP has updated from previous screenshots).

    DynDNS (3).png

    I've tried configuring the WAN interface initially to DHCP, then to StaticIP after setting a permanent lease within the router. Same problem occurs with both configurations. It had worked previously on an older router with PPPoE.
    I'm not 100% sure what to read from the logs but I've attached some below; I've edited the hostname for viewing purposes.

    PFSenseLogs DynDNS.txt

    Any help is hugely appreciated.

    V 1 Reply Last reply Feb 29, 2024, 7:15 PM Reply Quote 0
    • V
      viragomann @James92
      last edited by Feb 29, 2024, 7:15 PM

      @James92
      Seems your WAN IP changes quite often. You should rather address this issue, I think.

      J 1 Reply Last reply Mar 1, 2024, 7:56 AM Reply Quote 0
      • J
        James92 @viragomann
        last edited by James92 Mar 1, 2024, 7:56 AM Mar 1, 2024, 7:56 AM

        @viragomann That's due to me switching between DHCP and static to see if it made any difference. It's now set to static 192.168.2.50. Based on another forum post here and some on Reddit I suspect the problem is the new router (which is temporary, apparently) uses CG-NAT and it isn't configurable to that level unfortuantely.

        Thank you for replying, though

        1 Reply Last reply Reply Quote 0
        • J James92 referenced this topic on Mar 6, 2024, 2:31 PM
        1 out of 3
        • First post
          1/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received