HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- DNS performance
Windows Server 2003
1827491
Members
2383
Online
109965
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2007 08:49 AM
05-29-2007 08:49 AM
DNS performance
Hi,
I have a WIN 2003 with a DNS client performance that is worse than a HP-UX client.
How can I improve my DNS client performance at Windows 2003 Server?
I have a WIN 2003 with a DNS client performance that is worse than a HP-UX client.
How can I improve my DNS client performance at Windows 2003 Server?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2007 10:16 AM
05-29-2007 10:16 AM
Re: DNS performance
Can you describe the problem that you have, maybe posting results of commands?
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.
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.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2007 06:35 PM
05-29-2007 06:35 PM
Re: DNS performance
A useful command when troubleshooting DNS from a client's point of view is also to do the following:
ipconfig /flushdns
nslookup
set d2
www.hp.com (for example)
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.
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.
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:
http://support.microsoft.com/kb/321045
and
http://support.microsoft.com/kb/329982
Produces a nice html report with yellow and red colored text for any problems found.
Cheers,
Rune
ipconfig /flushdns
nslookup
set d2
www.hp.com (for example)
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.
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.
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:
http://support.microsoft.com/kb/321045
and
http://support.microsoft.com/kb/329982
Produces a nice html report with yellow and red colored text for any problems found.
Cheers,
Rune
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2007 12:58 AM
06-20-2007 12:58 AM
Re: DNS performance
Hi rune..
I hope yours wil be fine for this issue............ Good Keep it up.........
I hope yours wil be fine for this issue............ Good Keep it up.........
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP