Results 1 to 8 of 8
  1. #1

    How many NS can you use?


    I use Namecheap right now, and you can use up to 5 DNS in their preferences.

    Can you use 2 different web hosts?


    and thereby split traffic between different webhosts"?

  2. #2
    Join Date
    Feb 2003
    Kuala Lumpur, Malaysia
    No, you won't be able to split the traffic. Only load balancing hardware would be able to do so.

    Normally people do that to have separated NS instead of hosting all domains on the same server.

  3. #3
    Join Date
    Jan 2004
    Orlando, FL
    It is possible to have different DNS servers point to different web servers so that the traffic is shared. This is easily done.


  4. #4
    Join Date
    May 2001


    And yes this is load balanced so you need to keep two copies of the sites on two servers ~ If one server goes down, the other one takes over all the load.

  5. #5

    Look at Round Robin DNS; but there are issues.

    I found to be of interest specifically at the "Round-robin DNS" section.

    It did point out the following:

    === START CLIP ===

    "First, load balancing is only performed once for each client at the beginning of a session.

    Second, it's possible for the load balancing scheme to get a little skewed.

    For instance, all the users that have been sent to MyServer1 may go to lunch while all the users who have been sent to MyServer2 continue to send requests. In this case, one server could become overloaded while another server is sitting by idly.

    Third, A more significant problem with session-based load balancing is that it exposes the IP addresses of the servers in the farm to the client-side browser.

    What happens when a server crashes or is taken offline? Your balancing algorithm needs to account for this as soon as possible, but doing so can be problematic. If you're passing out bad IP addresses, your users will start to receive "server not available" errors.

    In a round-robin DNS system, it still can take as long as 48 hours to fix the problem once you've discovered that one of your servers has crashed.

    This is due to the fact that the changes to your IP address mappings need to be propagated to DNS servers throughout the Internet."

    === END CLIP === also does a good job at reporting the problems of DNS-based methods of load balancing:

    === START CLIP ===

    1. The time to live (TTL) on the zone files needs to be turned down severely to to reduce the time for which results are cached.

    The longer the TTL, the less control there is over which IP addresses that end-users are accessing. The shorter that TTL, the greater the potential for congestion on the DNS server.

    2. Users may access servers using an IP address rather than a host name.

    3. Users may use non-DNS methods such as an /etc/hosts file to map server host names to IP addresses.

    4. An additional problem with round-robin DNS is that the DNS daemon cannot differentiate between a request for a one-off hit, and a request that will result in many hits. That is, it is hard to control the granularity of scheduling.

    5. When using round-robin DNS there is no way to assign weights to servers, all servers will theoretically receive the same number of requests, regardless of their resources and current load.

    === END CLIP ===

    BTW, is an ok article on this subject.

    Thank you.
    Peter M. Abraham
    LinkedIn Profile

  6. #6
    Join Date
    Oct 2002
    EU - east side
    That last link did not work. Perhaps this is the article dynamicnet was referring to:

    Otherwise a very nice post dynamicnet, really informative!

  7. #7
    Thanks everyone!

  8. #8
    Join Date
    Apr 2004
    And yes this is load balanced so you need to keep two copies of the sites on two servers ~ If one server goes down, the other one takes over all the load.
    Doesnt work well with websites with databases, unless its remote.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts