<?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 &amp;amp; cache in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-amp-cache/m-p/2960738#M814210</link>
    <description>I have found the solution.&lt;BR /&gt;This often indicates that the glue record in the XXX.com domain doesn't match the record on the authoritative server. For instance, maybe on the authoritative server, ns1.XXX.com is an alias instead of an A record.&lt;BR /&gt;&lt;BR /&gt;Sergejs&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 29 Apr 2003 05:21:49 GMT</pubDate>
    <dc:creator>Sergejs Svitnevs</dc:creator>
    <dc:date>2003-04-29T05:21:49Z</dc:date>
    <item>
      <title>DNS &amp; cache</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-amp-cache/m-p/2960735#M814207</link>
      <description>Usually with some domains, I obtain a SERVFAIL when I make queries. To resolve it, I have to flush the cache (rndc flush). During 5-6 min., after flushing the cache, the server answers correctly.&lt;BR /&gt;&lt;BR /&gt;Example:&lt;BR /&gt;&lt;BR /&gt;before "rndc flush":&lt;BR /&gt;---named_dump.db&lt;BR /&gt;XXX.com  86310  IN NS  ns1.XXX.com.&lt;BR /&gt;&lt;BR /&gt;after "rndc flush" and "dig host.XXX.com":&lt;BR /&gt;---named_dump.db&lt;BR /&gt;XXX.com 85964 IN NS ns1.XXX.com.&lt;BR /&gt;ns1.XXX.com. 164 IN A &lt;IP_ADDRESS&gt; &lt;BR /&gt;&lt;BR /&gt;What should be the problem?&lt;BR /&gt;XXX.com is served by ns1.XXX.com. Where is A record for the name server?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Sergejs&lt;/IP_ADDRESS&gt;</description>
      <pubDate>Mon, 28 Apr 2003 15:53:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-amp-cache/m-p/2960735#M814207</guid>
      <dc:creator>Sergejs Svitnevs</dc:creator>
      <dc:date>2003-04-28T15:53:23Z</dc:date>
    </item>
    <item>
      <title>Re: DNS &amp; cache</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-amp-cache/m-p/2960736#M814208</link>
      <description>Try changing refrace value to smaller may be two hour or so.&lt;BR /&gt;&lt;BR /&gt;I have set for 6 hour.&lt;BR /&gt;21601   ; Refresh every 6 hours&lt;BR /&gt;&lt;BR /&gt;It is third line is SOA record.&lt;BR /&gt;&lt;BR /&gt;Sachin</description>
      <pubDate>Mon, 28 Apr 2003 16:43:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-amp-cache/m-p/2960736#M814208</guid>
      <dc:creator>Sachin Patel</dc:creator>
      <dc:date>2003-04-28T16:43:29Z</dc:date>
    </item>
    <item>
      <title>Re: DNS &amp; cache</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-amp-cache/m-p/2960737#M814209</link>
      <description>Sergejs,&lt;BR /&gt;&lt;BR /&gt;The real problem is with the sites that have servers that aren't available often, in which those DNS Admins should be changing the TTL to a smaller value!&lt;BR /&gt;&lt;BR /&gt;In your case add the $TTL directive to the beginning of your zone files.&lt;BR /&gt;&lt;BR /&gt;In this thread I compiled the info to build a DNS Caching Server.&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xdb005fe8b250d71190080090279cd0f9,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xdb005fe8b250d71190080090279cd0f9,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;live free or die</description>
      <pubDate>Mon, 28 Apr 2003 17:56:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-amp-cache/m-p/2960737#M814209</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2003-04-28T17:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: DNS &amp; cache</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-amp-cache/m-p/2960738#M814210</link>
      <description>I have found the solution.&lt;BR /&gt;This often indicates that the glue record in the XXX.com domain doesn't match the record on the authoritative server. For instance, maybe on the authoritative server, ns1.XXX.com is an alias instead of an A record.&lt;BR /&gt;&lt;BR /&gt;Sergejs&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Apr 2003 05:21:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-amp-cache/m-p/2960738#M814210</guid>
      <dc:creator>Sergejs Svitnevs</dc:creator>
      <dc:date>2003-04-29T05:21:49Z</dc:date>
    </item>
  </channel>
</rss>

