#DYN UPDATER NOT LOGING IN HOW TO#
#DYN UPDATER NOT LOGING IN PLUS#

#DYN UPDATER NOT LOGING IN HOW TO#

At this point my primary concern is how to get pfsense to recognize the fact that the IP has changed, and to update to use the cached IP, as I am not sure in some case that the IP simply changes that it will detect the change without having the correct last cached IP to point to.ĪSIDE: I have not masked IPs as they are dynamic and have since been changed.Īny ideas on how to resolve this 'cryptic' answer :

One last thing - I tried releasing WAN3 and connecting again and the cached IP did not change and once again NameCheap was updated. The issues appear to be around the where the response is not understood - but if I look at the response nothing looks off in it (of course nothing obvious) Nov 27 21:30:16 php-fpm 354 /rc.newwanip: phpDynDNS (): (Unknown Response) Nov 27 21:30:20 php-fpmĔ9592 /rc.start_packages: Restarting/Starting all packages. Nov 27 21:30:19 check_reload_statusĔ18 Starting packages

#DYN UPDATER NOT LOGING IN PLUS#

Nov 27 21:30:19 php-fpmē54 /rc.newwanip: Netgate pfSense Plus package system has detected an IP change or dynamic WAN reconnection - 174.91.131.176 -> 174.91.131.148 - Restarting packages. Nov 27 21:30:17 php-fpmē54 /rc.newwanip: Creating rrd update script Nov 27 21:30:17 php-fpmē54 /rc.newwanip: Resyncing OpenVPN instances for interface WAN3. Nov 27 21:30:16 php-fpmē54 /rc.newwanip: phpDynDNS (*): (Unknown Response) Nov 27 21:30:14 php-fpmē54 /rc.newwanip: phpDynDNS (Unknown Response) Nov 27 21:30:14 php-fpmē54 /rc.newwanip: phpDynDNS PAYLOAD: Nov 27 21:30:13 php-fpmē54 /rc.newwanip: phpDynDNS (www): (Unknown Response) Nov 27 21:30:13 php-fpmē54 /rc.newwanip: phpDynDNS (www): PAYLOAD: Here are the corresponding logs with 174.91.131.176 being the old IP and 174.91.131.148 the NEW IP. However, then I released the WAN3 IP and connected again and while the IP once again was updated in NameCheap DNS the entries once again appear in red and moreover the cached entries show the old IP address that correspond to the previous IP addresses in red: I did that and hit refresh on the page and Cached IP turned green and there was a checkmark. One suggestion was to correct these IP's and all might be well. When I created 3 Dynamic DNS (1 for each A-Record) on the FailoverWAN the DNS in Namecheap was updated correctly to my WAN3 (Tier 1) IP however all cached IP entries were 0.0.0.0Īfter reading some articles in this forum I found that the 3 corresponding cache files had entries in /cf/conf of form: The two DNS servers are 216.146.35.35 and 216.146.36.36.I have defined a gateway group called: FailoverWAN I highly recommend that if you use DynDNS, go check your servers now, make sure that you have 5.3.1, and uncheck that option ASAP! On an Active Directory-joined server this will make the server unable to communicate with a domain controller and things like NPS will stop working immediately. This update makes the option 'Use Dyn Recursive DNS servers on this machine' default, and puts their two DNS servers in front of any other DNS servers you have configured on the server's NICs. This means you might have the client installed on domain-joined computers. I know a lot of people use this for Internet failover situations so if they fail over to a backup Internet connection inbound NATs will also fail over to the new Internet connection. Last night DynDNS rolled out version 5.3.1 of their DynDNS Updater tool that is installed on a computer and keeps a DNS name updated with the correct IP.

Dyn updater not loging in