Regression #12631
closed
Dynamic DNS may not use the correct interface when updating during failover
100%
Description
Using 2.5.2-RELEASE
I have two interfaces - One WAN (gigabit) and a 4G Data Cell Link (150Mbps) as a secondary.
The WAN is Tier 1 and 4G is Tier 2 in a Gateway Group for failover.
If WAN 1 is unplugged, the 4G failover works no problem, however DynamicDNS fails to work - reporting that there is no response from NoIP (dyndns URL) - and the DNS record is not updated.
The same Dynamic update works if the WAN connection is reconnected. The default routing path is set to the Routing Group (and also tested with Automatic - but no effect).
If however the CUSTOM Dynamic DNS option is selected, you get an extra box for "Which Interface to send update from" - which I select the Routing Group - after adding the manual update URL string for NoIP, the updating on failover works perfectly.
It appears that all the standard Dynamic DNS providers are not updating/obeying the routing setup (so possibly using the standard WAN as the only interface).
Any suggestions welcome - happy to put up a config or activity log as this is in a non-production environment.
Related issues
Updated by Neill Lawson-Smith over 2 years ago
So an update....
I found that the Dynamic DNS option for "Custom" displays a drop down for "Interface to send update from" that is not available on any of the other Dynamic DNS providers. I noted that this defaults to the "Wan" interface rather than the Gateway Group as expected.
A workaround for this is to backup your config as an XML file, edit the XML file with a text editor, and look for the <dyndns> section (mine was towards the bottom) - under the XML config data for the Dynamic DNS provider that you have setup (do set it up beforehand), there is a tag <requestif>Wan</requestif> which records the Interface to send the request updates from - I changed mine to <requestif>AutoFailoverGateway</requestif> (my Gateway Group is called "AutoFailoverGateway"), then restore the config file - and hey presto, it works as expected.
So the bug is that the "Interface to send update from" field needs to be available for all Dynamic DNS Providers so that this can be set within the Admin interface.
Hope that helps everyone who comes across this
Updated by Viktor Gurov over 2 years ago
- Tracker changed from Bug to Regression
- Affected Version set to 2.5.2
Updated by Viktor Gurov over 2 years ago
- Related to Bug #9641: Dynamic DNS cannot update AAAA records on 6rd tunnel interfaces bound to PPPoE interfaces added
Updated by Viktor Gurov over 2 years ago
Updated by Jim Pingle over 2 years ago
- Status changed from New to Pull Request Review
- Target version set to CE-Next
- Plus Target Version set to 22.05
Updated by Jim Pingle over 2 years ago
- Target version changed from CE-Next to 2.6.0
- Plus Target Version changed from 22.05 to 22.01
Updated by Viktor Gurov over 2 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
Applied in changeset c3474eef834d4b77631e961c5569254a8094b12f.
Updated by Jim Pingle over 2 years ago
- Subject changed from Default Route Not Used Properly for Dynamic DNS in Failover to Dynamic DNS may not use the correct interface for making updates during failover
Updating subject for release notes.
Updated by Jim Pingle over 2 years ago
- Subject changed from Dynamic DNS may not use the correct interface for making updates during failover to Dynamic DNS may not use the correct interface when updating during failover
Updated by Viktor Gurov about 2 years ago
- Is duplicate of Bug #11958: Multi-wan Azure Dyndns updates not working when primary WAN is unplugged added