DrayTek UK Users' Community Forum
Help, Advice and Solutions from DrayTek Users
2862 Domain-name based WAN Routing not working as expected
- John
- Topic Author
- Offline
- Junior Member
Less
More
- Posts: 30
- Thank you received: 2
05 Aug 2024 11:04 - 05 Aug 2024 14:39 #103556
by John
2862 Domain-name based WAN Routing not working as expected was created by John
ConfigurationWAN1 – ADSL WAN2 – Ethernet DHCP
Firmware is 3.9.9.4_BT.
Load Balance / Route Policy
Destination – Domain NamePolicy set to route to the following over WAN2 as preferred interface; *.apple.com, *.icloud.com, *.wetransfer.com, *.onedrive.com
And for this to fail back to WAN1 (since WAN2 is not always available).
Problem
Using traceroute to check, only traffic to wetransfer.com actually routes via WAN2.
I’ve tried clearing DNS caches on client machines, but that doesn’t work.
Also, WAN routing based on source IP works seamlessly.
I'd appreciate any ideas to fix this!
Firmware is 3.9.9.4_BT.
Load Balance / Route Policy
Destination – Domain NamePolicy set to route to the following over WAN2 as preferred interface; *.apple.com, *.icloud.com, *.wetransfer.com, *.onedrive.com
And for this to fail back to WAN1 (since WAN2 is not always available).
Problem
Using traceroute to check, only traffic to wetransfer.com actually routes via WAN2.
I’ve tried clearing DNS caches on client machines, but that doesn’t work.
Also, WAN routing based on source IP works seamlessly.
I'd appreciate any ideas to fix this!
Last edit: 05 Aug 2024 14:39 by John. Reason: Format
Please Log in or Create an account to join the conversation.
- John
- Topic Author
- Offline
- Junior Member
Less
More
- Posts: 30
- Thank you received: 2
05 Aug 2024 16:31 #103559
by John
Replied by John on topic 2862 Domain-name based WAN Routing not working as expected
Looking further at this, using traceroute,
1 192.168.0.1 (192.168.0.1) 12.223 ms 3.565 ms 4.234 ms
2 172.20.10.1 6.933 ms
xxx.xxx.xxx.xxx 21.622 ms 22.292 ms
1st response is from the router’s LAN IP address
2nd responses are from firstly the WAN2 gateway and secondly from the WAN1 gateway. The subsequent responses are from the WAN1 route to the target.
That’s with the priority of the Policy set to 1, but that doesn’t seem to make a difference. The diagnostic rule checker on the router seems to skip the policy and use a lower one.
1 192.168.0.1 (192.168.0.1) 12.223 ms 3.565 ms 4.234 ms
2 172.20.10.1 6.933 ms
xxx.xxx.xxx.xxx 21.622 ms 22.292 ms
1st response is from the router’s LAN IP address
2nd responses are from firstly the WAN2 gateway and secondly from the WAN1 gateway. The subsequent responses are from the WAN1 route to the target.
That’s with the priority of the Policy set to 1, but that doesn’t seem to make a difference. The diagnostic rule checker on the router seems to skip the policy and use a lower one.
Please Log in or Create an account to join the conversation.
- John
- Topic Author
- Offline
- Junior Member
Less
More
- Posts: 30
- Thank you received: 2
23 Aug 2024 17:16 - 23 Aug 2024 21:09 #103657
by John
Replied by John on topic 2862 Domain-name based WAN Routing not working as expected
I now think that a routing rule such as *.domain.com correctly routes sub-domains of domain.com but doesn't catch the case where * is null and therefore doesn't route domain.com as expected.
Subject to further testing.
Tested with firmware 3.9.9.5_BT
Subject to further testing.
Tested with firmware 3.9.9.5_BT
Last edit: 23 Aug 2024 21:09 by John. Reason: Added Firmware Version Tested
Please Log in or Create an account to join the conversation.
Moderators: Chris, Sami
Copyright © 2024 DrayTek