|
|
 |  |
Re: Load Balancing questionFrom: Men & Mice Support Date: Wednesday, July 3, 2002
Time: 12:22:16 pmOK, let's go over the various problems present.
1. Not all of these domains use load balancing. For example,
officefurniturerep.com does not.
2. Only one of your DNS servers has the load balance record,
ns1.infoedg.com. The others, including ns2.infoedg.com, do not,
meaning that if ns1 goes down, all load balancing stops.
3. The TTL of your load balance record is 86400. This is far too high
for a load balance record. Change it to something short, such as 300
seconds.
The combination of items 2 and 3 means that your slave servers, of
which you have three, will cache one of the IP addresses of your
websites, and they'll do so for up to 24 hours. Thus even when the
master server is working, there isn't much load balancing or fault
tolerance going on.
If the main web server goes down, the master DNS server will start
giving out the IP address of the other web server. If this goes on
for a sufficiently long time, the slave DNS servers will eventually
cache this IP address, and will then continue to give it out for the
following 24 hours, regardless of whether the main web server comes
back up again.
____________________________________________________________________
Chris Buxton Men & Mice
support@menandmice.com Making DNS Easy
At 2:55 PM +0800 7/3/02, Suzanne Swift wrote:
>Here are the names we were testing:
>
>yoma.com
>boydlighting.com
>riviera-usa.com
>furniture-office.com
>infoedg.com
>officefurniturerep.com
>adi-artdesign.com
>
>>This sounds like a misconfiguration of the slave DNS server, along
>>with possibly a caching issue. Can you give us one or more of the
>>website names in question?
>>____________________________________________________________________
>>Chris Buxton Men & Mice
>>support@menandmice.com Making DNS Easy
>>
>>At 9:19 AM +0800 7/3/02, Suzanne Swift wrote:
>>>I have two Web servers A and B. Quick DNS is set up to load balance so that
>>>99% of the load goes to A and 1 % to B.
>>>
>>>I ran a DNS system test and took my primary DNS server off-line.
>>>Both Web server A & B were still on-line. When I did a DNS
>>>look-up for four of my host names - all were being pointed at
>>>server B (the 1% server).
>>>
>>>I then turned the primary DNS server back on and checked 7 hosts. 5 were
>>>now pointing at server B and two at server A.
>>>
>>>I checked again the next morning and six domains were pointing at
>>>server B and
>>>only one at server A.
>>>
>>>Finally, approximately 24 hours or so after turning the primary load server
>>>on and off, I checked the seven host names again: all seven were now
>>>pointing at server A.
>>>
>>>My primary host name settings (I run virtual hosting) are:
>>>
>>>Refresh: 28800
>>>Retry: 7200
>>>Expire: 604800
>>>Minimum: 86400
>>>Time-to-live: 86400
>>>
>>>The Load balance record settings are:
>>>
>>>Interval: 30
>>>Hostlife: 60
>>>
>>>
>>>My question is: Why does the DNS shift the load to Server B when
>>>the Primary DNS machine goes down? Is there any way to prevent
>>>this from happening?
>>>--
>>>Thanks,
>>>Suzanne
|

Return to Digital Point Solutions' Home Page |