Bug #14605
openDynamic DNS uses the default gateway interface instead of the specified interface when behind NAT
0%
Description
- Configure a gateway group with WAN1 (tier 1) and WAN2 (tier 2), and set it as the default system gateway.
- Configure Dynamic DNS on WAN2.
This results in DDNS using the current default gateway (WAN1) instead of the specified interface (WAN2).
Files
Related issues
Updated by Marcos M 11 months ago
- Related to Feature #14610: Add source address option to Check IP Services added
Updated by Danilo Zrenjanin 11 months ago
I followed the steps to reproduce the issue. However, in my case, the Dynamic DNS used the WAN2 as defined.
1. Configured Gateway Group and defined it as the default gateway for the firewall.
2. Defined Dynamic DNS setup using Digital Ocean as the service type and set WAN2 for the Interface.
3. On the upstream device, I blocked all the traffic for the WAN1 interface (except ICMP to keep the WAN1 up).
4. The Dynamic DNS server regularly updated the A record using the WAN2 interface.
5. I was able to capture packets on the WAN2 during the Dynamic DNS update process.
Updated by Stepan Afonin 6 months ago
- File asiabell.jpg asiabell.jpg added
- File beeline.jpg beeline.jpg added
- File dyndns.jpg dyndns.jpg added
- File gw groups.jpg gw groups.jpg added
- File states error.jpg states error.jpg added
Good afternoon. I can confirm that there is an error, but for some reason netgate does not want to investigate it (if I’m wrong, please tell me, is it not configured correctly? The change request comes from the default gateway, but from ip wan2(opt1)
I use netgate 6100 equipment with version 23.09.1
Updated by Stepan Afonin 6 months ago
- File default gw group.jpg default gw group.jpg added
- File gw groups.jpg gw groups.jpg added