Regression #13862: Dynamic DNS check IP address service fails when using the default service - pfSense - pfSense bugtracker

Actions

Copy link

Regression #13862

closed

Dynamic DNS check IP address service fails when using the default service

Added by M Felden almost 2 years ago. Updated almost 2 years ago.

Status:

Resolved

Priority:

High

Assignee:

Jim Pingle

Category:

Dynamic DNS

Target version:

2.7.0

Start date:

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

23.01

Release Notes:

Force Exclusion

Affected Version:

Affected Architecture:

Actions

Copy link

Updated by M Felden almost 2 years ago

Replicated on SG-1100 and two whitebox installs now:

Current Base System
23.01.b.20230106.0600
Latest Base System
23.01.b.20230106.0600

WAN IPv4 is RFC1918 (in a hotel)

DynDNS not updating since upgrade from 22.05. DNS lookups work. CheckIP service is resolvable, reachable and works:

curl -s http://checkip.dyndns.com
<html><head><title>Current IP Check</title></head><body>Current IP Address: 209.3.185.234</body></html>

Log claims it cannot figure the IPv4 address via the checkip service:

Jan 12 05:13:23     php-fpm     381     /services_dyndns_edit.php: Dynamic DNS (demobox.mfld-pub.net) There was an error trying to determine the public IP for interface - wan (mvneta0.4090 ).
Jan 12 05:13:23     php-fpm     381     /services_dyndns_edit.php: Dynamic DNS (demobox.mfld-pub.net): running get_failover_interface for wan. found mvneta0.4090
Jan 12 05:13:23     php-fpm     381     /services_dyndns_edit.php: Dynamic DNS cloudflare (demobox.mfld-pub.net): Public IP address could not be extracted from Check IP Service
Jan 12 05:13:22     php-fpm     381     /services_dyndns_edit.php: Dynamic DNS cloudflare (demobox.mfld-pub.net): _checkIP() starting.
Jan 12 05:13:22     php-fpm     381     /services_dyndns_edit.php: Dynamic DNS: updatedns() starting
Jan 12 05:13:22     php-fpm     381     /services_dyndns_edit.php: Configuration Change: admin@172.16.110.101 (Local Database): Dynamic DNS client configured.
Jan 12 05:13:00     php-fpm     4335     /services_dyndns.php: Dynamic DNS (demobox.mfld-pub.net) There was an error trying to determine the public IP for interface - wan (mvneta0.4090 ).
Jan 12 05:13:00     php-fpm     4335     /services_dyndns.php: Dynamic DNS (demobox.mfld-pub.net): running get_failover_interface for wan. found mvneta0.4090
Jan 12 05:13:00     php-fpm     4335     /services_dyndns.php: Dynamic DNS cloudflare (demobox.mfld-pub.net): Public IP address could not be extracted from Check IP Service

Actions

Copy link

Updated by Lev Prokofev almost 2 years ago

Tested on

23.05-DEVELOPMENT (amd64)
built on Mon Jan 09 06:04:59 UTC 2023
FreeBSD 14.0-CURRENT

Can confirm that behavior when the WAN IP is RFC1918, on my edge with a "white" IP it works as expected with 23.01, however, it's not working on the device behind the NAT on 23.01 but works on 22.05. Tested under 3 services - freeDNS, Namecheap,DNSexit

/services_dyndns_edit.php: Dynamic DNS (prokleon.mooo.com) There was an error trying to determine the public IP for interface - wan (igb0 ).
/services_dyndns_edit.php: Dynamic DNS freedns (prokleon.mooo.com): Public IP address could not be extracted from Check IP Service

/services_dyndns_edit.php: Dynamic DNS (lev.run.place) There was an error trying to determine the public IP for interface - wan (igb0 ).
/services_dyndns_edit.php: Dynamic DNS dnsexit (lev.run.place): Public IP address could not be extracted from Check IP Service

/services_dyndns.php: Dynamic DNS (pf.prokleon.xyz) There was an error trying to determine the public IP for interface - wan (igb0 ).
/services_dyndns.php: Dynamic DNS namecheap (pf.prokleon.xyz): Public IP address could not be extracted from Check IP Service

Actions

Copy link

Updated by Jim Pingle almost 2 years ago

Project changed from pfSense Plus to pfSense
Category changed from Dynamic DNS to Dynamic DNS
Assignee set to Jim Pingle

This was working recently (Around December 21, when I fixed the Check IP service selection in 1670f4c028141eec106ca275b52474b03794eb1c ). I'll look into it again.

Actions

Copy link

Updated by Jim Pingle almost 2 years ago

Subject changed from DynDNS claims cannot determine WAN IP when WAN is RFC1918 and external service is relied upon to Dynamic DNS check IP address service fails when using the default service
Priority changed from Low to High
Target version set to 2.7.0
Plus Target Version set to 23.01

I see the problem, when trying to include the default check IP service in the list of available services, it's not properly adding the default service to the list.

To me, I have a fix.

Actions

Copy link