Take note that more info is returned, only the first array line is shown.Ĭheck with if your parameters are ok (password and domain name). Or it did return (the beginning of the payload) "". Namecheap should return 'something with the error count (after xml parsing) set to zero, and in that case the meassage "IP Address Updated Successfully!" is returned, and successful_update is set to "true".
#Dyn updater not updating update
So that explains why you saw an initial "0.0.0.0|xxxxxxxxx" - and why the file didn't get updated.Īt line 2324 you can see what must happen, so pfSEnse knows if the update was successful : If that's also true, then the file(s) is/are updated. The cache files, one for IPv4 or IPv6 (if your using IPv6) is only updated if the update (against namecheap) was 'successful_update' must be 'true'.Īnd if it was true, read on a line or two, and find the simple test checks if the WAN IP is NOT zero '0'.
#Dyn updater not updating 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 updating 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: I have defined a gateway group called: FailoverWAN
0 kommentar(er)
