<?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: DNS in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dns/m-p/2466454#M597633</link>
    <description>Thanks. You guys are smart.&lt;BR /&gt;&lt;BR /&gt;Happy thanks giving.&lt;BR /&gt;&lt;BR /&gt;...Madhu</description>
    <pubDate>Thu, 23 Nov 2000 00:34:38 GMT</pubDate>
    <dc:creator>Madhu Sudhan_1</dc:creator>
    <dc:date>2000-11-23T00:34:38Z</dc:date>
    <item>
      <title>DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns/m-p/2466451#M597630</link>
      <description>How does load balancing of web sites work if a particular domain called &lt;A href="http://www.itplindia.com" target="_blank"&gt;www.itplindia.com&lt;/A&gt; have two ip addresses. &lt;BR /&gt;1)Internet name servers allow this kind of facility ? &lt;BR /&gt;&lt;BR /&gt;If so,&lt;BR /&gt;&lt;BR /&gt;2)How does the resolution happen in this case ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 22 Nov 2000 00:37:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns/m-p/2466451#M597630</guid>
      <dc:creator>Madhu Sudhan_1</dc:creator>
      <dc:date>2000-11-22T00:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns/m-p/2466452#M597631</link>
      <description>Normally this is what happens:&lt;BR /&gt;&lt;BR /&gt;In this example assume that the web-server has to 'A' records in DNS (eg. 10.0.0.1 and 10.0.0.2).&lt;BR /&gt;&lt;BR /&gt;The DNS server returns *both* addresses. 50% of the times the .1 address is listed first and 50% the .2 address is listed first.&lt;BR /&gt;&lt;BR /&gt;This is what is called round-robin.&lt;BR /&gt;&lt;BR /&gt;All Bind implementations behave like this unless the DNS-admin specify a specific 'sortlist'.</description>
      <pubDate>Wed, 22 Nov 2000 13:28:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns/m-p/2466452#M597631</guid>
      <dc:creator>Lasse Knudsen</dc:creator>
      <dc:date>2000-11-22T13:28:32Z</dc:date>
    </item>
    <item>
      <title>Re: DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns/m-p/2466453#M597632</link>
      <description>Madhu,&lt;BR /&gt;&lt;BR /&gt;The web server can have multiple NICs or IP Aliases associated with it.  DNS will attempt two things:&lt;BR /&gt;&lt;BR /&gt;1. To provide the address which matches the network of the requester (or some reasonable approximate answer closest to the IP Address of the requestor).&lt;BR /&gt;&lt;BR /&gt;2. DNS will also attempt to 'alternate' between the two interfaces if they are on the same network, or if the network of the requestor does not match one of the answers.&lt;BR /&gt;&lt;BR /&gt;Hope that helps!&lt;BR /&gt;&lt;BR /&gt;Happy Thanksgiving!</description>
      <pubDate>Wed, 22 Nov 2000 14:17:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns/m-p/2466453#M597632</guid>
      <dc:creator>Albert E. Whale, CISSP</dc:creator>
      <dc:date>2000-11-22T14:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns/m-p/2466454#M597633</link>
      <description>Thanks. You guys are smart.&lt;BR /&gt;&lt;BR /&gt;Happy thanks giving.&lt;BR /&gt;&lt;BR /&gt;...Madhu</description>
      <pubDate>Thu, 23 Nov 2000 00:34:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns/m-p/2466454#M597633</guid>
      <dc:creator>Madhu Sudhan_1</dc:creator>
      <dc:date>2000-11-23T00:34:38Z</dc:date>
    </item>
  </channel>
</rss>

