<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: round-robin in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132049#M571192</link>
    <description>I have read somewhere that it's recommended to use dig instead of nslookup!&lt;BR /&gt;</description>
    <pubDate>Mon, 01 Dec 2003 03:27:45 GMT</pubDate>
    <dc:creator>Norman_21</dc:creator>
    <dc:date>2003-12-01T03:27:45Z</dc:date>
    <item>
      <title>round-robin</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132041#M571184</link>
      <description>I'm trying the DNS round-robin function, assume the A hostname, has 3 ip-address, 10.1.1.1 and 10.1.1.2 and 10.1.1.3, in BIND 8.12, while nslookup A, it cound be found by 10.1.1.1 10.1.1.2 10.1.1.3 by order, but when I upgrate to BIND9.2, the nslookup A would not get the order, it will get the random order, such as 10.1.1.2 10.1.1.1 10.1.1.3.... Does any one has the experience about BIND9.2 round-robin?</description>
      <pubDate>Sun, 30 Nov 2003 22:17:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132041#M571184</guid>
      <dc:creator>j773303</dc:creator>
      <dc:date>2003-11-30T22:17:50Z</dc:date>
    </item>
    <item>
      <title>Re: round-robin</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132042#M571185</link>
      <description>Have a look at this posting:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=202397" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=202397&lt;/A&gt;</description>
      <pubDate>Sun, 30 Nov 2003 22:32:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132042#M571185</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2003-11-30T22:32:06Z</dc:date>
    </item>
    <item>
      <title>Re: round-robin</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132043#M571186</link>
      <description>I'm not sure the configuration problem. But now the nslookup the get random order, so the BIND 9.2 round-robin has enabled. My mean is why BIND 9.2 round-robin is rand order search? Does any one has the same problem? Or this is a featuer or bug in BIND 9.2?</description>
      <pubDate>Sun, 30 Nov 2003 22:45:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132043#M571186</guid>
      <dc:creator>j773303</dc:creator>
      <dc:date>2003-11-30T22:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: round-robin</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132044#M571187</link>
      <description>Does anyone has the experience configure round-robin in BIND 9.2? What's your nslookup hostname search order?</description>
      <pubDate>Mon, 01 Dec 2003 01:21:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132044#M571187</guid>
      <dc:creator>j773303</dc:creator>
      <dc:date>2003-12-01T01:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: round-robin</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132045#M571188</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;This is from the Release notes of Bind 9.2&lt;BR /&gt;Unsupported Features&lt;BR /&gt;The following BIND 8.1.2 options are not supported in BIND 9.2.0:&lt;BR /&gt;â ¢ no-round-robin&lt;BR /&gt;This option was used in BIND 8.1.2 to turn off the default round&lt;BR /&gt;robin, which cycles returned IP addresses for multi-homed hosts.&lt;BR /&gt;&lt;BR /&gt;Look here, page 21:&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/B5969-4338/B5969-4338.pdf" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/B5969-4338/B5969-4338.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this help&lt;BR /&gt;Btw: what version are you runnin</description>
      <pubDate>Mon, 01 Dec 2003 01:42:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132045#M571188</guid>
      <dc:creator>Norman_21</dc:creator>
      <dc:date>2003-12-01T01:42:52Z</dc:date>
    </item>
    <item>
      <title>Re: round-robin</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132046#M571189</link>
      <description>&lt;BR /&gt;Another release note for 11.0&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/5969-4366/5969-4366.html" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/5969-4366/5969-4366.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Dec 2003 01:47:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132046#M571189</guid>
      <dc:creator>Norman_21</dc:creator>
      <dc:date>2003-12-01T01:47:01Z</dc:date>
    </item>
    <item>
      <title>Re: round-robin</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132047#M571190</link>
      <description>The code in Bind 9.0 was changed so that the nameserver doesn't have to keep track of&lt;BR /&gt;state regarding which "position" the rotary is in at any given point in time.&lt;BR /&gt;&lt;BR /&gt;in Bind 8.x RRSET-ORDER option defines the order in which multiple records of the same type are returned.&lt;BR /&gt;&lt;BR /&gt;RRSET-ORDER IS NOT YET IMPLEMENTED IN BIND 9.&lt;BR /&gt;&lt;BR /&gt;Current BIND implementations return multiple records using a random-cyclic order (the starting address is randomly chosen and thereafter round-robin order).&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sergejs</description>
      <pubDate>Mon, 01 Dec 2003 02:43:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132047#M571190</guid>
      <dc:creator>Sergejs Svitnevs</dc:creator>
      <dc:date>2003-12-01T02:43:41Z</dc:date>
    </item>
    <item>
      <title>Re: round-robin</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132048#M571191</link>
      <description>Thank you all for the good suggestions. I'm still have concern, that's meaning load-lancing for round-robin, if BIND9.X support round-robin, but get the random order, that's means the nslookup Ahost would get the same ip-address even if configure 3 ip-adress for Ahost. But in BIND 8.X, the round-robin will fit the load-balancing function. Any one can tell me, why BIND9.x modify the code for round-robin (load-balancing)? How does BIND9.x reached the load-balancing?</description>
      <pubDate>Mon, 01 Dec 2003 02:58:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132048#M571191</guid>
      <dc:creator>j773303</dc:creator>
      <dc:date>2003-12-01T02:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: round-robin</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132049#M571192</link>
      <description>I have read somewhere that it's recommended to use dig instead of nslookup!&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Dec 2003 03:27:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132049#M571192</guid>
      <dc:creator>Norman_21</dc:creator>
      <dc:date>2003-12-01T03:27:45Z</dc:date>
    </item>
    <item>
      <title>Re: round-robin</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132050#M571193</link>
      <description>For the inbound load balancing and redundancy of your servers I suggest that you look into the "real" Load Balancing/Distribution Solutions (Alteon switches, Cisco LocalDirector, &lt;A href="http://www.linux-vs.org," target="_blank"&gt;www.linux-vs.org,&lt;/A&gt; &lt;A href="http://www.redhat.com/support/wpapers/piranha/,....)." target="_blank"&gt;http://www.redhat.com/support/wpapers/piranha/,....).&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sergejs&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Dec 2003 04:09:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132050#M571193</guid>
      <dc:creator>Sergejs Svitnevs</dc:creator>
      <dc:date>2003-12-01T04:09:25Z</dc:date>
    </item>
    <item>
      <title>Re: round-robin</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132051#M571194</link>
      <description>Hmm, I think with bind9 all is working just fine. You may ask from yourself, what is the goal of the round robin? Answer is to reduce traffic for those hosts. You see, on huge corporations there is always a problem, when it come's to reaching some host (read hostname) over internet and here come's to aid round robin. Let's assume that one hosts is daily in overload. Administrator then divides this traffic to multiple physical hosts (eg. 10.1.1.2 etc.) where runs original hosts mirrored webservice or smth. When someone tries access from internet to that hosts it gets to one of these hosts dynamically. But when some physical host dies then DNS don'nt know anything about that. Unfortunatelly here come's administrator again to favor, it musts wipe out that hosts address from dns round robin.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;Sander</description>
      <pubDate>Tue, 23 Mar 2004 17:22:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/round-robin/m-p/3132051#M571194</guid>
      <dc:creator>Sander Sokk</dc:creator>
      <dc:date>2004-03-23T17:22:26Z</dc:date>
    </item>
  </channel>
</rss>

