Abuse issue with dyndns on nsupdate.info



  • Hi all

    I'm pretty new to pfSense. So please bear with me… I googled and searched this forum but did not find an answer yet

    I'm using nsupdate.info for dyndns. They provide setup information for pfSense, so I assume that the setup is correct. The dyndns actually works and I can access the device from remote even thought the page Services: Dynamic DNS clients shows cached IP 0.0.0.0 in red which I assume should show the public IP.

    The real problem now is that pfSense sends updates to nsupdate too often even if the IP address did not change. (It actually changes very seldom if at all). In the log files I see all too often the line

    check_reload_status: updating dyndns WAN_DHCP
    

    together with

    check_reload_status: Reloading filter
    check_reload_status: Restarting OpenVPN tunnels/interfaces
    check_reload_status: Restarting ipsec tunnels
    

    It appears in irregular intervals of a few minutes, sometimes even twice in the same minute and then not for a few hours. So far I could not figure out what is causing this frequent check_reload_status. I have also checked the DHCP log entries for dhclient. But there are only a few and by far less frequent than the check_reload_status entries.

    Example:

    
    dhclient[15057]: bound to xx.xx.xx.129 -- renewal in 43200 seconds.
    dhclient: Creating resolv.conf
    dhclient: /sbin/route add default xx.xx.xx.1
    dhclient: Adding new routes to interface: re0
    dhclient: New Routers (re0): xx.xx.xx.1
    dhclient: New Broadcast Address (re0): 255.255.255.255
    dhclient: New Subnet Mask (re0): 255.255.240.0
    dhclient: New IP Address (re0): xx.xx.xx.129
    dhclient: ifconfig re0 inet xx.xx.xx.129 netmask 255.255.240.0 broadcast 255.255.255.255
    dhclient: Starting add_new_address()
    dhclient: REBOOT
    dhclient[15057]: DHCPACK from xx.xx.128.1
    dhclient[15057]: DHCPREQUEST on re0 to 255.255.255.255 port 67
    dhclient: PREINIT
    dhclient[35822]: exiting.
    dhclient[35822]: connection closed
    

    Does anyone have an idea what could cause the frequent dyndns updates resulting in abuse blocking? Or what I could do to debug this issue further? I'll happily provide further details.

    My setup is the following:
    Cable modem in bridged mode (pfSense is getting public IP from DHCP), cable provider is UPC Cablecom
    pfSense runs 2 VLANs on the LAN and an openVPN Server

    Thanks in advance!



  • @FreeMinded:

    … The dyndns actually works and I can access the device from remote even thought the page Services: Dynamic DNS clients shows cached IP 0.0.0.0 in red which I assume should show the public IP.

    I found the solution to this problem.
    The field result match in the Dynamic DNS configuration should contain

    good %IP%|nochg %IP%
    

    With that the correct IP is displayed.


Log in to reply