traffic dedication

[AndrewFram]

We have a 3060Pro Enhanced with two WANs; a T1 as the primary and Cable as the secondary. There are two things I want to do.

1. Put the WANs in a round robin failover so I can dedicate traffic types over one of the two (sonicwall says the round robin is required for this). If I do this, some of our email starts to bounce because the reverse DNS lookups start to fail. Do I need a reverse DNS entry for the secondary WAN, or would it be better to create a route for SMTP to be dedicated to the primary WAN?

2. I want to make a route policy for all HTTP traffic to go over the secondary WAN because it's much faster for downloads. When I enable round robin and follow sonicwall's instructions, DNS no longer seems to work, and no one can browse the web. As soon as I shut the route off, everything works fine again. Any ideas what I might be doing wrong?

 

[AndrewFram]

I created the route to push all HTTP traffic on the second WAN and created another route to push all SMTP traffic on the primary WAN.

The reason why people couldn't access the web was because I needed to specify SECONDARY GATEWAY in the route for the HTTP rule (I had DEFAULT GATEWAY).

 

[cajuntank]

You probably need to do the same for https. I had the same problem when I cofigured my first sonicwall a couple of years ago for load balancing instead of just failover. I had people accessing ssl sites and having issues half the time. The connection would be started out of one interface and then try to load balance out of the other interface. The SSL site of course was seeing a session trying to cut in from another address since it had already estatblished the secure connection with the first address.