I have a Balance One and have a question about the outbound policies that use DNS hostnames. Is this correlating IP addresses by doing a reverse lookup only? I ask because I am trying to balance (1:1 weights) for game and content download for my xbox. The hostname that the xbox uses never matches up to a reverse lookup since the content is coming from a CDN. The following names are fictional since I don’t want to break any TOS with Xbox live.
Let’s say the xbox downloads game titles from games.xbox.com. When I try to use this as the DNS name for outbound policy - it doesn’t work. I see the connections in the active sessions on the wrong WAN. I always wait a full minute after applying config changes to make sure that I don’t have any persistent sessions getting it stuck.
What I think is happening is the following…
Xbox requests DNS entry for games.xbox.com
Xbox gets results that look like
games.xbox.com -> someserver.region.xbox.cdn.com -> actualserver.cdn.net -> 220.127.116.11
Xbox makes request to 18.104.22.168 -
Peplink does reverse lookup and sees actualserver.cdn.net (which doesn’t match the rule)
Peplink routes down wrong WAN
Basically, even though the Peplink is what told the Xbox that games.xbox.com is 22.214.171.124; it doesn’t know the information when it is time to do the routing for that host. I tested my theories by changing the domain name in the outbound policy to match what is returned with the reverse lookup and my traffic was balanced as expected. This is not ideal since the Xbox can use several different CDNs, but they will all be a product of the forward resolved address for games.xbox.com.
Any help is appreciated.