Load Balancer (Piranha) node different VLAN best practice

I have a load balancer (piranha) and I added a server behind (the VIP) that sits on a different vlan/network. I found out after I added the node that load balancer is producing network time out. I'm not sure why sits doing that so I remove the server I just added and tested its network connection. I see it responding perfectly without any problem. I'm not sure what's the best practice for piranha load balancer but is it allowed(or is it best practice) to have nodes behind the vip from different network subnet/vlan?

So this is what it looks like
Current Nodes behind the vip:,,
New Node I added behind the VIP:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Does the path to the new ip exists from the loadbalancer side?
Often you want to limit the discrepancies/differences.
I.e. The path to same network is direct, the path to a different segment/VLAN has the packet going through the default gateway and back and is susceptible to restrictions.
Some might be implemented down the line impacting the one node in that range.
SuperRootAuthor Commented:
ahh yeah they have different gateway IP but its both managed by the same firewall. I guess it won't work on the load balancer?  

Current Nodes behind the vip:,,
Has a gateway of

New Node I added behind the VIP:
Has a gateway of
Multi segment load balancer could work as long as it has a path and a path back.

Best  practices depend on the requirements, available resources,etc.
if one has unlimited, one would usually have two of each 2xlb HA, 2 switches interconnected, etc. power feed from different sources/breakers....
SuperRootAuthor Commented:
I can verify that piranha servers can ping the new DNS server from a different vlan. I also see DNS ports open from the piranha load balancer servers to the new DNS server. I'm not really sure why load balancer is timing out after I added the new server. I talked to my network engineer and he said for 17 years of network experience this is the first time he sets this up. He said load balancer nodes should only be sitting on one network vlan otherwise it'll be hard to manage. I agree but we want to migrate all our DNS server to this new vlan network slowly. We just don't do big migration change. We do it slowly.
DNS is not one of those services that need to be behind loadbalancers.  Usually DNS should be on different segments.
The way the load balancer vip is define is to pass both TCP and udp?

Do you gave the option to define two DNS virtual ports on your load balancer?
The DNS zone/s will reflect both and you can transition at your own pace adding nodes to the new one while decommissioning nodes from the old one.

Unfortunately, your question might be looking for a solution of, given the addition of a new separate segment node, there is an intermittent issue that comes up for access to that node.
I.e. When does that occur what is the test/query when this occurs, source of the query.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.