Bug #16259
closed
DynDNS is unable to get the IPv6 address from the WASN Interface
Added by Claude Robitaille 3 months ago.
Updated 3 months ago.
Description
DynDNS seems unable to retrieve the IPv6 address in order to update the DNS server.
Jun 11 15:07:37 main php-fpm92235: /rc.newwanipv6: phpDynDNS (demo.nearedge.io): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Jun 11 15:07:38 main php-fpm99896: /rc.dyndns.update: Dynamic DNS (trial.nearedge.io) There was an error trying to determine the public IP for interface - wan (pppoe1 ).
- Status changed from New to Not a Bug
If a gateway is associated with the interface and that gateway is unavailable (e.g. offline) then DDNS won't work.
This is the WAN interface and it is up and running, including accessing the gateway. Internet over IPv6 works perfectly well at the time of DDNS,
Can confirm this issue appeared for me upon update to 2.8.0. Worked fine under 2.7.2.
In my setup, WAN is pppoe0.
/services_dyndns_edit.php: Dynamic DNS (pfsense.example.com) There was an error trying to determine the public IP for interface - wan (pppoe0 ).
Occurs under both normal and kernel-mode PPPoE.
The link-local ISP gateway (e.g. fe80::2e0:4cff:fe20:1476%pppoe0) does not respond to pings over IPv6 for some reason and thus appears down, but this has been the case before under 2.7.2 for > 6 months and there was no problem with Dynamic DNS.
IPv6 internet access works fine, and the assigned WAN IPv6 address (via DHCPv6 over PPPoE) can be pinged externally.
Setting a monitor IP for the IPv6 gateway to the ISP's DNS server appears to be a valid workaround.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by