blaster998
asked on
Can I set up NLB with a server that has a dynamic IP assigned by no-ip.com
I have 2 identical servers that I am putting on load balancing for. They both have windows 2003 V2 on them. The IP addresses are dynamic but both have no-ip.com on them so they both have "static IP" addresses from no-ip.com that resolve to the dynamic IP addresses of the servers so that no matter what internal IP addresses the servers have, you can find them using the static IP addresses assigned by no-ip.com
For example, after installing the software of no-ip.com, I can use XXXXX.serveftp.com (a domain owned by no-ip.com to always reference and find my server.
Will I still be able to do network load balancing on these 2 servers? My sys admin says I need static IP addresses, however, the static IP addresses from no-ip.com should do the trick, shouldn't they?
For example, after installing the software of no-ip.com, I can use XXXXX.serveftp.com (a domain owned by no-ip.com to always reference and find my server.
Will I still be able to do network load balancing on these 2 servers? My sys admin says I need static IP addresses, however, the static IP addresses from no-ip.com should do the trick, shouldn't they?
Andrej Pirman
Probably NO, because most of NLB mechanisms are using IP's, not FQDN, but it still depends on what NLB you had in mind - for outgoing traffic, mail, or web or what?
ASKER
The purpose is to balance the processing being done by the server's CPU. Its not web traffic but rather a process I have running
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The question still is....for NLB to work, do you need static IP addresses, or can you use internal IP addresses for your devices. My sys admin is saying I need static IP addresses, I'm looking for a second opinion.
We have a website that exchanges a lot of data between it and our server. We're trying to distribute the load between the 2 servers.
We have a website that exchanges a lot of data between it and our server. We're trying to distribute the load between the 2 servers.
All still depends on many factors, among which top question is what device/mechanism you intend to use for NLB?
You may want to do NLB on public internet links so to distribute traffic among many internet lines. In this case you may go:
1.) On CLIENT side (web server side) programm the application that way, to use Round-Robin for traffic distribution with some cehcking mechanism, which tries connection prior to sending data (to avoid timeouts).
2.) You may go simlpe Roaund-Robin using 2 or more A-records in DNS, which all point to different IP's of your 2 or more receiving servers. This is, as I say, simple Round-robin and does NOT check whether line or server is busy, but instead sends one package to first server, and another to second and so on. This MIGHT work with Dyn-DNS, too, having in mind timeouts in times of IP change.
I am not familliar enough with Dyn-DNS, but for this to work, Dyn-DNS client application should support 2 or more of SAME A-records (or CNAME-records) to be entered on 2 or more servers in such a way, that duplicate A or CNAME records would not replace each other, but rather add one to another to have Round-robin principle.
But none of above principles do any checks of internet line busy status, neither of target server's CPU usage. they simply distribute traffic evenly among 2 or more destinations.
So to have better distribution of actual LOAD between 2 servers, you might employ some other principle, where you would have 1 entry point for all traffic, and then program some load distribution mechanism inside your LAN to evenly fill up both servers. But sollution here depends on the nature of your goal, what traffic to distribute, which level of knowledge you have and so on.
You may want to do NLB on public internet links so to distribute traffic among many internet lines. In this case you may go:
1.) On CLIENT side (web server side) programm the application that way, to use Round-Robin for traffic distribution with some cehcking mechanism, which tries connection prior to sending data (to avoid timeouts).
2.) You may go simlpe Roaund-Robin using 2 or more A-records in DNS, which all point to different IP's of your 2 or more receiving servers. This is, as I say, simple Round-robin and does NOT check whether line or server is busy, but instead sends one package to first server, and another to second and so on. This MIGHT work with Dyn-DNS, too, having in mind timeouts in times of IP change.
I am not familliar enough with Dyn-DNS, but for this to work, Dyn-DNS client application should support 2 or more of SAME A-records (or CNAME-records) to be entered on 2 or more servers in such a way, that duplicate A or CNAME records would not replace each other, but rather add one to another to have Round-robin principle.
But none of above principles do any checks of internet line busy status, neither of target server's CPU usage. they simply distribute traffic evenly among 2 or more destinations.
So to have better distribution of actual LOAD between 2 servers, you might employ some other principle, where you would have 1 entry point for all traffic, and then program some load distribution mechanism inside your LAN to evenly fill up both servers. But sollution here depends on the nature of your goal, what traffic to distribute, which level of knowledge you have and so on.