<?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 DNS TTL Time in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-ttl-time/m-p/3718659#M252373</link>
    <description>Dear Sirs,&lt;BR /&gt;&lt;BR /&gt;Our web applications are configured for Geographic load balancing. In case one environment is not available, the traffic will route to another GeO.&lt;BR /&gt;&lt;BR /&gt;My apprehension is, DNS has TTL time and it will hold the traffic for that period. I believe, in most of the environment DNS servers TTL time is 4 minute. That means switching over next &lt;BR /&gt;Geo will not be detected upto 4 minute.&lt;BR /&gt;&lt;BR /&gt;Am i correct or misunderstood this concept ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv</description>
    <pubDate>Fri, 27 Jan 2006 00:24:17 GMT</pubDate>
    <dc:creator>Shivkumar</dc:creator>
    <dc:date>2006-01-27T00:24:17Z</dc:date>
    <item>
      <title>DNS TTL Time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-ttl-time/m-p/3718659#M252373</link>
      <description>Dear Sirs,&lt;BR /&gt;&lt;BR /&gt;Our web applications are configured for Geographic load balancing. In case one environment is not available, the traffic will route to another GeO.&lt;BR /&gt;&lt;BR /&gt;My apprehension is, DNS has TTL time and it will hold the traffic for that period. I believe, in most of the environment DNS servers TTL time is 4 minute. That means switching over next &lt;BR /&gt;Geo will not be detected upto 4 minute.&lt;BR /&gt;&lt;BR /&gt;Am i correct or misunderstood this concept ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv</description>
      <pubDate>Fri, 27 Jan 2006 00:24:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-ttl-time/m-p/3718659#M252373</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2006-01-27T00:24:17Z</dc:date>
    </item>
    <item>
      <title>Re: &#xD;
DNS TTL Time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-ttl-time/m-p/3718660#M252374</link>
      <description>Hi Shiv, &lt;BR /&gt;&lt;BR /&gt;TTL (Time To Live)  is a limit on the period of time that a unit of data (e.g. a record) can exist before it is discarded also, Specifying the amount of time other DNS servers and applications are allowed to cache the record. &lt;BR /&gt;&lt;BR /&gt;You can find more information about DNS TTL, &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.simpledns.com/help/index.html?df_ttl.htm" target="_blank"&gt;http://www.simpledns.com/help/index.html?df_ttl.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-Arun</description>
      <pubDate>Fri, 27 Jan 2006 00:37:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-ttl-time/m-p/3718660#M252374</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2006-01-27T00:37:06Z</dc:date>
    </item>
    <item>
      <title>Re: &#xD;
DNS TTL Time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-ttl-time/m-p/3718661#M252375</link>
      <description>hi Shiv,&lt;BR /&gt;&lt;BR /&gt;Each domain name has one or more Resource Records (RRs) associated with it. Resource records are 5-tuples:&lt;BR /&gt;    Domain_name  TTL  Type  Class  Value&lt;BR /&gt;&lt;BR /&gt;TTL&lt;BR /&gt;is the Time To Live of this RR. When this RR is returned as a result of a DNS lookup, the remote host normally caches the information for efficiency. The TTL is the time, in seconds, after which the cached information should be regarded as potentially out of date.&lt;BR /&gt;&lt;BR /&gt;Hence, a change will definitely help in your case.&lt;BR /&gt;&lt;BR /&gt;kind regards&lt;BR /&gt;yogeeraj</description>
      <pubDate>Fri, 27 Jan 2006 01:12:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-ttl-time/m-p/3718661#M252375</guid>
      <dc:creator>Yogeeraj_1</dc:creator>
      <dc:date>2006-01-27T01:12:45Z</dc:date>
    </item>
    <item>
      <title>Re: &#xD;
DNS TTL Time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-ttl-time/m-p/3718662#M252376</link>
      <description>Hi Shiv, &lt;BR /&gt;&lt;BR /&gt;Another good link about TTL concept, &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.zytrax.com/books/dns/apa/ttl.html" target="_blank"&gt;http://www.zytrax.com/books/dns/apa/ttl.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-Arun</description>
      <pubDate>Fri, 27 Jan 2006 01:39:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-ttl-time/m-p/3718662#M252376</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2006-01-27T01:39:39Z</dc:date>
    </item>
    <item>
      <title>Re: &#xD;
DNS TTL Time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-ttl-time/m-p/3718663#M252377</link>
      <description>TTL is related caching the DNS recored informations. &lt;BR /&gt;&lt;BR /&gt;Time To Live, the number of seconds remaining on a cached record before it is purged. For authoritative records the TTL is fixed at a specific length. If a record is cached, the server providing the record will provide the time remaining on the TTL rather then the original length it was given.&lt;BR /&gt;&lt;BR /&gt;A good explanation. Refer here at &lt;A href="http://www.menandmice.com/online_docs_and_faq/glossary/glossarytoc.htm?ttl.htm." target="_blank"&gt;http://www.menandmice.com/online_docs_and_faq/glossary/glossarytoc.htm?ttl.htm.&lt;/A&gt; Use hyper links to learn more.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Muthu</description>
      <pubDate>Fri, 27 Jan 2006 01:49:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-ttl-time/m-p/3718663#M252377</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2006-01-27T01:49:08Z</dc:date>
    </item>
  </channel>
</rss>

