<?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 performance in Windows Server 2003</title>
    <link>https://community.hpe.com/t5/windows-server-2003/dns-performance/m-p/4009373#M4253</link>
    <description>A useful command when troubleshooting DNS from a client's point of view is also to do the following:&lt;BR /&gt;&lt;BR /&gt;ipconfig /flushdns&lt;BR /&gt;nslookup&lt;BR /&gt;set d2&lt;BR /&gt;&lt;A href="http://www.hp.com" target="_blank"&gt;www.hp.com&lt;/A&gt;  (for example)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The "set d2" will give you detailed information about which servers the client queries - including which order and also show the suffixes it tries to append etc.&lt;BR /&gt;&lt;BR /&gt;The ipconfig /flushdns is necessary to ensure the client does not use cached lookups. Be aware of the effect of caching - if the UX client has cached lookups it will be quicker when comparing to other clients that do not have cached lookups.&lt;BR /&gt;&lt;BR /&gt;For further troubleshootin of your DNS servers please check out the DNSLINT utility from MS.  This does a number of automated tests on your DNS servers which is both quicker and more reliable than doing it manually.  See: &lt;BR /&gt;&lt;A href="http://support.microsoft.com/kb/321045" target="_blank"&gt;http://support.microsoft.com/kb/321045&lt;/A&gt;&lt;BR /&gt;and&lt;BR /&gt;&lt;A href="http://support.microsoft.com/kb/329982" target="_blank"&gt;http://support.microsoft.com/kb/329982&lt;/A&gt;&lt;BR /&gt;Produces a nice html report with yellow and red colored text for any problems found.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Rune&lt;BR /&gt;</description>
    <pubDate>Wed, 30 May 2007 01:35:34 GMT</pubDate>
    <dc:creator>Rune J. Winje</dc:creator>
    <dc:date>2007-05-30T01:35:34Z</dc:date>
    <item>
      <title>DNS performance</title>
      <link>https://community.hpe.com/t5/windows-server-2003/dns-performance/m-p/4009371#M4251</link>
      <description>Hi,&lt;BR /&gt;I have a WIN 2003 with a DNS client performance that is worse than a HP-UX client.&lt;BR /&gt;How can I improve my DNS client performance at Windows 2003 Server?</description>
      <pubDate>Tue, 29 May 2007 15:49:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/dns-performance/m-p/4009371#M4251</guid>
      <dc:creator>Nilzelio Monteiro_1</dc:creator>
      <dc:date>2007-05-29T15:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: DNS performance</title>
      <link>https://community.hpe.com/t5/windows-server-2003/dns-performance/m-p/4009372#M4252</link>
      <description>Can you describe the problem that you have, maybe posting results of commands?&lt;BR /&gt;&lt;BR /&gt;Check your DNS suffix in "My computer" properties. Also check the "Append these DNS suffixes" and "DNS suffix for this connection" in TCP/IP properties.</description>
      <pubDate>Tue, 29 May 2007 17:16:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/dns-performance/m-p/4009372#M4252</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2007-05-29T17:16:27Z</dc:date>
    </item>
    <item>
      <title>Re: DNS performance</title>
      <link>https://community.hpe.com/t5/windows-server-2003/dns-performance/m-p/4009373#M4253</link>
      <description>A useful command when troubleshooting DNS from a client's point of view is also to do the following:&lt;BR /&gt;&lt;BR /&gt;ipconfig /flushdns&lt;BR /&gt;nslookup&lt;BR /&gt;set d2&lt;BR /&gt;&lt;A href="http://www.hp.com" target="_blank"&gt;www.hp.com&lt;/A&gt;  (for example)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The "set d2" will give you detailed information about which servers the client queries - including which order and also show the suffixes it tries to append etc.&lt;BR /&gt;&lt;BR /&gt;The ipconfig /flushdns is necessary to ensure the client does not use cached lookups. Be aware of the effect of caching - if the UX client has cached lookups it will be quicker when comparing to other clients that do not have cached lookups.&lt;BR /&gt;&lt;BR /&gt;For further troubleshootin of your DNS servers please check out the DNSLINT utility from MS.  This does a number of automated tests on your DNS servers which is both quicker and more reliable than doing it manually.  See: &lt;BR /&gt;&lt;A href="http://support.microsoft.com/kb/321045" target="_blank"&gt;http://support.microsoft.com/kb/321045&lt;/A&gt;&lt;BR /&gt;and&lt;BR /&gt;&lt;A href="http://support.microsoft.com/kb/329982" target="_blank"&gt;http://support.microsoft.com/kb/329982&lt;/A&gt;&lt;BR /&gt;Produces a nice html report with yellow and red colored text for any problems found.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Rune&lt;BR /&gt;</description>
      <pubDate>Wed, 30 May 2007 01:35:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/dns-performance/m-p/4009373#M4253</guid>
      <dc:creator>Rune J. Winje</dc:creator>
      <dc:date>2007-05-30T01:35:34Z</dc:date>
    </item>
    <item>
      <title>Re: DNS performance</title>
      <link>https://community.hpe.com/t5/windows-server-2003/dns-performance/m-p/4009374#M4254</link>
      <description>Hi rune..&lt;BR /&gt;&lt;BR /&gt;   I hope yours wil be fine for this issue............ Good Keep it up.........</description>
      <pubDate>Wed, 20 Jun 2007 07:58:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/dns-performance/m-p/4009374#M4254</guid>
      <dc:creator>Antony I Louis</dc:creator>
      <dc:date>2007-06-20T07:58:09Z</dc:date>
    </item>
  </channel>
</rss>

