Project

General

Profile

Actions
Copy link

Bug #14605

open

Dynamic DNS uses the default gateway interface instead of the specified interface

Added by Marcos M over 1 year ago. Updated 19 days ago.

Status:
Pull Request Review
Priority:
Normal
Assignee:
Marcos M
Category:
Dynamic DNS
Target version:
2.8.0
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
25.01
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

Steps:
  1. Configure a gateway group with WAN1 (tier 1) and WAN2 (tier 2), and set it as the default system gateway.
  2. Configure Dynamic DNS on WAN2.

This results in DDNS using the current default gateway (WAN1) instead of the specified interface (WAN2).

Files

Download all files
asiabell.jpg (46.3 KB) asiabell.jpg Stepan Afonin, 12/30/2023 05:16 AM
beeline.jpg (49.2 KB) beeline.jpg Stepan Afonin, 12/30/2023 05:16 AM
dyndns.jpg (46.7 KB) dyndns.jpg Stepan Afonin, 12/30/2023 05:16 AM
gw groups.jpg (15.4 KB) gw groups.jpg Stepan Afonin, 12/30/2023 05:16 AM
states error.jpg (124 KB) states error.jpg Stepan Afonin, 12/30/2023 05:16 AM
default gw group.jpg (42.1 KB) default gw group.jpg Stepan Afonin, 12/30/2023 05:29 AM
gw groups.jpg (72.5 KB) gw groups.jpg Stepan Afonin, 12/30/2023 05:29 AM

Related issues

Related to Feature #14610: Add source address option to Check IP ServicesClosedMarcos M

Actions
Actions
Copy link
 #1

Updated by Marcos M over 1 year ago

  • Subject changed from Dynamic DNS does not ignore gateway group when set to a specific interface to Dynamic DNS always uses the default gateway interface instead of the specified interface
Actions
Copy link
 #2

Updated by Marcos M over 1 year ago

This seems to be due to the Check IP Service using the default gateway which happens because the WANs are both RFC1918.

Actions
Copy link
 #3

Updated by Marcos M over 1 year ago

  • Related to Feature #14610: Add source address option to Check IP Services added
Actions
Copy link
 #4

Updated by Danilo Zrenjanin over 1 year 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.

Actions
Copy link
 #5

Updated by Marcos M over 1 year ago

  • Subject changed from Dynamic DNS always uses the default gateway interface instead of the specified interface to Dynamic DNS uses the default gateway interface instead of the specified interface when behind NAT
Actions
Copy link
 #6

Updated by Stepan Afonin 11 months ago

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

Actions
Copy link
 #8

Updated by Marcos M 19 days ago

  • Subject changed from Dynamic DNS uses the default gateway interface instead of the specified interface when behind NAT to Dynamic DNS uses the default gateway interface instead of the specified interface
  • Status changed from New to Pull Request Review
  • Assignee set to Marcos M
  • Target version set to 2.8.0
  • Plus Target Version set to 25.01
Actions
Copy link

Also available in: Atom PDF